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

Bulk-authorize push devices before notification fan-out #725

New Issue
Closed
opened 2026-08-13 09:20:23 +00:00 by timmy · 0 comments
timmy commented 2026-08-13 09:20:23 +00:00
Owner
Copy Link

Problem

Unread and deadline push delivery authorizes device sessions serially before bounded provider fan-out. Each device opens SQLite independently, delaying every healthy notification as subscriptions grow.

Product slice

Authorize claimed device management IDs in one bounded registry operation, reuse the status map across fan-out, prune inactive subscriptions, and remain fail-closed if the registry cannot be read. Apply the same behavior to unread updates and deadline reminders.

Acceptance criteria

  • One bulk session-registry read authorizes a dispatch batch; no per-device registry loop.
  • Active, idle, expired, revoked, and unknown devices preserve existing authorization semantics.
  • Inactive subscriptions are removed while active siblings still receive notifications.
  • Registry failure sends nothing, preserves subscriptions/checkpoints, releases leases, and permits retry.
  • Duplicate IDs and empty batches are deterministic.
  • Behavioral tests cover session-store, unread, and deadline paths and the full suite passes.
## Problem Unread and deadline push delivery authorizes device sessions serially before bounded provider fan-out. Each device opens SQLite independently, delaying every healthy notification as subscriptions grow. ## Product slice Authorize claimed device management IDs in one bounded registry operation, reuse the status map across fan-out, prune inactive subscriptions, and remain fail-closed if the registry cannot be read. Apply the same behavior to unread updates and deadline reminders. ## Acceptance criteria - One bulk session-registry read authorizes a dispatch batch; no per-device registry loop. - Active, idle, expired, revoked, and unknown devices preserve existing authorization semantics. - Inactive subscriptions are removed while active siblings still receive notifications. - Registry failure sends nothing, preserves subscriptions/checkpoints, releases leases, and permits retry. - Duplicate IDs and empty batches are deterministic. - Behavioral tests cover session-store, unread, and deadline paths and the full suite passes.
timmy self-assigned this 2026-08-13 09:20:23 +00:00
timmy closed this issue 2026-08-13 09:31:46 +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#725
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?