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

fix: Bound event stream refresh latency #59

Merged
timmy merged 1 commits from timmy/58-bound-event-stream-refresh-latency into main 2026-08-06 01:19:22 +00:00
Conversation 0 Commits 1 Files Changed 2 +46 -2
timmy commented 2026-08-06 01:18:49 +00:00
Owner
Copy Link

Closes #58

Caps stalled Gitea event refreshes at five seconds, cancels upstream work, and returns a retryable 503 response.

Tests: pytest -q (40 passed).

Closes #58 Caps stalled Gitea event refreshes at five seconds, cancels upstream work, and returns a retryable 503 response. Tests: `pytest -q` (40 passed).
timmy added 1 commit 2026-08-06 01:18:50 +00:00
fix: bound event stream refresh latency (#58)
All checks were successful
CI / lint (pull_request) Successful in 8s
Details
CI / build-frontend (pull_request) Successful in 4s
Details
a173182158
timmy merged commit 36f500d58b into main 2026-08-06 01:19:22 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
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
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#59
No description provided.
Delete Branch "timmy/58-bound-event-stream-refresh-latency"

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?