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

Isolate and bound deadline reminder delivery #711

New Issue
Closed
opened 2026-08-13 05:48:53 +00:00 by timmy · 0 comments
timmy commented 2026-08-13 05:48:53 +00:00
Owner
Copy Link

Problem

Deadline reminders share one dispatch lease and one poll exception boundary with unread-update push. A broken unread snapshot skips reminders, while slow serial deadline fan-out can outlive its lease and permit duplicate sends.

Scope

  • isolate unread and deadline poll failures
  • use channel-scoped renewable leases
  • bound deadline device fan-out with per-device failure isolation

Acceptance

  • unread failure does not skip deadline dispatch
  • unread and deadline channels can hold leases concurrently; same-channel workers cannot
  • deadline fan-out honors configured concurrency and healthy devices survive a failed sibling
  • lease ownership is renewed through fan-out to prevent duplicate delivery
  • focused and full test suites pass

Discovered against origin/main c503994. No matching open/closed issue title or recent commit was found; #709 added reminders but did not isolate or bound their dispatch.

## Problem Deadline reminders share one dispatch lease and one poll exception boundary with unread-update push. A broken unread snapshot skips reminders, while slow serial deadline fan-out can outlive its lease and permit duplicate sends. ## Scope - isolate unread and deadline poll failures - use channel-scoped renewable leases - bound deadline device fan-out with per-device failure isolation ## Acceptance - unread failure does not skip deadline dispatch - unread and deadline channels can hold leases concurrently; same-channel workers cannot - deadline fan-out honors configured concurrency and healthy devices survive a failed sibling - lease ownership is renewed through fan-out to prevent duplicate delivery - focused and full test suites pass Discovered against `origin/main` c503994. No matching open/closed issue title or recent commit was found; #709 added reminders but did not isolate or bound their dispatch.
timmy self-assigned this 2026-08-13 05:48:53 +00:00
timmy closed this issue 2026-08-13 05:59:03 +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#711
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?