stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Paginate the unread updates inbox without slowing live refresh #147

New Issue
Closed
opened 2026-08-06 23:21:29 +00:00 by timmy · 0 comments
timmy commented 2026-08-06 23:21:29 +00:00
Owner
Copy Link

Evidence

The live account currently has 210 unread Gitea notifications, while src/gitea_proxy.py requests only limit=50 and discards X-Total-Count. The mobile My Work UI presents that partial page as the complete inbox and says “Mark all,” leaving 160 updates undiscoverable. No open/closed issue title or recent commit covers notification pagination or completeness.

User flow

Keep the pooled live snapshot bounded to page 1, report “50 of 210 unread updates,” and let the user load subsequent pages on demand. Merge pages by notification ID, preserve loaded updates on retryable failures, and prevent duplicate concurrent loads.

Acceptance tests

  • Live snapshot fetches only page 1 and exposes total, page, and has_more.
  • A bounded no-store page endpoint loads only the requested next notification page.
  • Loading more merges unique IDs without refetching context or events.
  • Concurrent load-more taps are single-flight; errors retain existing updates and allow retry.
  • Final page removes the load action and reports the complete count.
  • Mobile controls are at least 44px and bulk acknowledgement remains capped at 50 loaded IDs.
## Evidence The live account currently has 210 unread Gitea notifications, while `src/gitea_proxy.py` requests only `limit=50` and discards `X-Total-Count`. The mobile My Work UI presents that partial page as the complete inbox and says “Mark all,” leaving 160 updates undiscoverable. No open/closed issue title or recent commit covers notification pagination or completeness. ## User flow Keep the pooled live snapshot bounded to page 1, report “50 of 210 unread updates,” and let the user load subsequent pages on demand. Merge pages by notification ID, preserve loaded updates on retryable failures, and prevent duplicate concurrent loads. ## Acceptance tests - Live snapshot fetches only page 1 and exposes `total`, `page`, and `has_more`. - A bounded no-store page endpoint loads only the requested next notification page. - Loading more merges unique IDs without refetching context or events. - Concurrent load-more taps are single-flight; errors retain existing updates and allow retry. - Final page removes the load action and reports the complete count. - Mobile controls are at least 44px and bulk acknowledgement remains capped at 50 loaded IDs.
timmy self-assigned this 2026-08-06 23:21:29 +00:00
timmy closed this issue 2026-08-06 23:31:28 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
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#147
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?