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

Run push notification channels on independent fixed cadences #713

New Issue
Closed
opened 2026-08-13 06:18:52 +00:00 by timmy · 0 comments
timmy commented 2026-08-13 06:18:52 +00:00
Owner
Copy Link

Problem

Unread-update delivery and deadline reminders share one sequential poll loop. A slow unread fan-out delays mobile deadline reminders, and each run's duration is added to the configured cadence.

Scope

Run unread updates and deadline reminders in independent, non-overlapping workers aligned to monotonic scheduled ticks. Preserve channel-specific leases, timeout/concurrency settings, session checks, and clean lifespan cancellation.

Acceptance criteria

  • A blocked unread dispatch does not delay a deadline dispatch.
  • A blocked deadline dispatch does not delay unread polling.
  • Short runs stay aligned to fixed scheduled ticks instead of completion-plus-interval drift.
  • Overruns never overlap within a channel or create catch-up bursts.
  • Lifespan cancellation awaits both workers cleanly.
  • Focused and full test suites pass.

Evidence

src/main.py currently awaits unread dispatch and then deadline dispatch in _push_poll_loop; existing issue #711 isolated exceptions and leases but intentionally retained sequential scheduling. No historical issue title or recent commit implements independent push channel workers.

## Problem Unread-update delivery and deadline reminders share one sequential poll loop. A slow unread fan-out delays mobile deadline reminders, and each run's duration is added to the configured cadence. ## Scope Run unread updates and deadline reminders in independent, non-overlapping workers aligned to monotonic scheduled ticks. Preserve channel-specific leases, timeout/concurrency settings, session checks, and clean lifespan cancellation. ## Acceptance criteria - A blocked unread dispatch does not delay a deadline dispatch. - A blocked deadline dispatch does not delay unread polling. - Short runs stay aligned to fixed scheduled ticks instead of completion-plus-interval drift. - Overruns never overlap within a channel or create catch-up bursts. - Lifespan cancellation awaits both workers cleanly. - Focused and full test suites pass. ## Evidence `src/main.py` currently awaits unread dispatch and then deadline dispatch in `_push_poll_loop`; existing issue #711 isolated exceptions and leases but intentionally retained sequential scheduling. No historical issue title or recent commit implements independent push channel workers.
timmy self-assigned this 2026-08-13 06:22:58 +00:00
timmy closed this issue 2026-08-13 06:25: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#713
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?