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

Serve retained live snapshots with stale-while-revalidate freshness #139

New Issue
Closed
opened 2026-08-06 21:25:24 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-06 21:25:24 +00:00
Member
Copy Link

Problem

Visible clients poll /api/v1/live every eight seconds. The server only coalesces overlapping requests and discards a completed snapshot, so sequential tabs each trigger the full Gitea fan-out and a brief upstream outage removes otherwise recent usable data.

User outcome

After the first successful load, dashboard refreshes are immediate and recent work/activity/notifications remain available while one background refresh revalidates them. Upstream fan-out is bounded by a server freshness window rather than active tab count.

Acceptance criteria

  • A cold request waits for one bounded live snapshot build.
  • Sequential requests inside the freshness window reuse the retained snapshot.
  • The first stale request starts one background refresh and immediately serves the last good snapshot; concurrent stale requests do not duplicate refreshes.
  • Successful refresh atomically replaces the retained snapshot and exposes freshness/revalidation metadata.
  • Failed refresh preserves the last good snapshot; cold-start failure remains a bounded 503.
  • Marking a notification read removes it from the retained snapshot immediately.
  • Live responses remain Cache-Control: no-store; shutdown cancels active refresh work.
  • Behavioral tests prove RED before implementation and the full suite passes.

Non-duplication evidence

Issues #119/#120 added visibility-aware client polling; #131/#132 added the unified endpoint and simultaneous request pooling; #137/#138 made pooled work cancellation-safe. None retains a completed snapshot, defines a freshness window, serves stale data during revalidation, or invalidates notifications after mutation.

## Problem Visible clients poll `/api/v1/live` every eight seconds. The server only coalesces overlapping requests and discards a completed snapshot, so sequential tabs each trigger the full Gitea fan-out and a brief upstream outage removes otherwise recent usable data. ## User outcome After the first successful load, dashboard refreshes are immediate and recent work/activity/notifications remain available while one background refresh revalidates them. Upstream fan-out is bounded by a server freshness window rather than active tab count. ## Acceptance criteria - A cold request waits for one bounded live snapshot build. - Sequential requests inside the freshness window reuse the retained snapshot. - The first stale request starts one background refresh and immediately serves the last good snapshot; concurrent stale requests do not duplicate refreshes. - Successful refresh atomically replaces the retained snapshot and exposes freshness/revalidation metadata. - Failed refresh preserves the last good snapshot; cold-start failure remains a bounded 503. - Marking a notification read removes it from the retained snapshot immediately. - Live responses remain `Cache-Control: no-store`; shutdown cancels active refresh work. - Behavioral tests prove RED before implementation and the full suite passes. ## Non-duplication evidence Issues #119/#120 added visibility-aware client polling; #131/#132 added the unified endpoint and simultaneous request pooling; #137/#138 made pooled work cancellation-safe. None retains a completed snapshot, defines a freshness window, serves stale data during revalidation, or invalidates notifications after mutation.
timmy was assigned by rockachopa 2026-08-06 21:25:37 +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#139
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?