Bound event stream refresh latency #58

Closed
opened 2026-08-06 01:17:34 +00:00 by timmy · 0 comments
Owner

Evidence: GET /api/v1/events directly awaits activity_events(), which performs two sequential Gitea calls, without an endpoint-level deadline. A stalled upstream can hold dashboard refresh requests beyond the five-second UI polling interval. Acceptance: cap event refresh latency, cancel stalled work, return a retryable 503 response with Retry-After, and preserve successful event responses.

Evidence: `GET /api/v1/events` directly awaits `activity_events()`, which performs two sequential Gitea calls, without an endpoint-level deadline. A stalled upstream can hold dashboard refresh requests beyond the five-second UI polling interval. Acceptance: cap event refresh latency, cancel stalled work, return a retryable 503 response with `Retry-After`, and preserve successful event responses.
timmy self-assigned this 2026-08-06 01:17:34 +00:00
timmy closed this issue 2026-08-06 01:19:22 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
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#58
No description provided.