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

Drain closed-app queued work concurrently without failure starvation #297

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

Problem

When connectivity returns after an operator queues several issues or replies offline and closes the app, Background Sync delivers records serially and aborts on the first transient failure. One slow or unavailable repository can strand unrelated queued work within the browser's bounded sync window.

Slice

  • Claim a finite, fair batch across issue and authored-message lanes.
  • Drain it with bounded concurrency.
  • Attempt each eligible record at most once per sync event.
  • Continue unrelated delivery after transient failures while preserving claim release, receipts, and idempotency keys.
  • Stop admission on authentication loss.

Acceptance

  • Delayed records execute concurrently without exceeding the configured bound.
  • A transiently failing record is released while healthy records in both lanes are delivered and receipted.
  • No record is retried in the same sync event.
  • Authentication loss stops new work and releases affected claims.
  • Focused tests and full suite pass.

Implementation must use strict test-first RED/GREEN and close this issue through a linked PR.

## Problem When connectivity returns after an operator queues several issues or replies offline and closes the app, Background Sync delivers records serially and aborts on the first transient failure. One slow or unavailable repository can strand unrelated queued work within the browser's bounded sync window. ## Slice - Claim a finite, fair batch across issue and authored-message lanes. - Drain it with bounded concurrency. - Attempt each eligible record at most once per sync event. - Continue unrelated delivery after transient failures while preserving claim release, receipts, and idempotency keys. - Stop admission on authentication loss. ## Acceptance - Delayed records execute concurrently without exceeding the configured bound. - A transiently failing record is released while healthy records in both lanes are delivered and receipted. - No record is retried in the same sync event. - Authentication loss stops new work and releases affected claims. - Focused tests and full suite pass. Implementation must use strict test-first RED/GREEN and close this issue through a linked PR.
timmy self-assigned this 2026-08-08 11:49:21 +00:00
timmy closed this issue 2026-08-08 11:57:10 +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#297
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?