Make partial mobile Search pagination retryable and lossless #807

Closed
opened 2026-08-14 07:21:07 +00:00 by timmy · 0 comments
Owner

Problem

Mobile Search uses one shared page across issue and pull streams. A transient failure can make partial results non-retryable or skip the recovered stream's first page. Odd limits also over-fetch both streams and truncate one valid result at each boundary.

User value

Operators can retry missing Search results in place without gaps, duplicates, or restarting their scoped query.

Acceptance criteria

  • Track issue and pull continuation independently.
  • A failed stream remains retryable at the same page while successful streams advance only from pages actually consumed.
  • Odd combined limits return contiguous results from both streams without dropping boundary items.
  • Mobile Search exposes a clear Retry missing results action for partial responses.
  • Query/scope changes still abort stale continuation requests.
  • Focused behavioral tests and the full suite pass.
## Problem Mobile Search uses one shared page across issue and pull streams. A transient failure can make partial results non-retryable or skip the recovered stream's first page. Odd limits also over-fetch both streams and truncate one valid result at each boundary. ## User value Operators can retry missing Search results in place without gaps, duplicates, or restarting their scoped query. ## Acceptance criteria - Track issue and pull continuation independently. - A failed stream remains retryable at the same page while successful streams advance only from pages actually consumed. - Odd combined limits return contiguous results from both streams without dropping boundary items. - Mobile Search exposes a clear **Retry missing results** action for partial responses. - Query/scope changes still abort stale continuation requests. - Focused behavioral tests and the full suite pass.
timmy self-assigned this 2026-08-14 07:21:07 +00:00
timmy closed this issue 2026-08-14 07:35:03 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#807
No description provided.