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

Bound aggregate Gitea traffic and coalesce concurrent reads #246

New Issue
Closed
opened 2026-08-08 00:28:36 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-08 00:28:36 +00:00
Member
Copy Link

Evidence

The shared Gitea AsyncClient has no application-level admission control, while search, detail, polling, and review flows fan out concurrent upstream requests. Feature-local limits do not bound aggregate traffic across tabs or preserve capacity for authored actions. No historical issue title or recent commit implements a transport-wide bulkhead or concurrent GET coalescing.

User value

Polling and read bursts cannot overwhelm Gitea or starve comments, reviews, and other mutations. Identical concurrent reads share one upstream call, while overload fails quickly and truthfully as retryable HTTP 503 instead of cascading into route timeouts.

Acceptance

  • Identical concurrent GETs execute once and return the same result to all callers.
  • Distinct reads never exceed the configured read capacity and saturated requests fail within the admission deadline.
  • Mutations are never coalesced and retain reserved capacity during read saturation.
  • Cancelling one GET waiter does not cancel work needed by other waiters.
  • Shutdown cancels shared requests before closing the HTTP client.
  • Configuration and retry behavior are documented; focused and full suites pass.
## Evidence The shared Gitea `AsyncClient` has no application-level admission control, while search, detail, polling, and review flows fan out concurrent upstream requests. Feature-local limits do not bound aggregate traffic across tabs or preserve capacity for authored actions. No historical issue title or recent commit implements a transport-wide bulkhead or concurrent GET coalescing. ## User value Polling and read bursts cannot overwhelm Gitea or starve comments, reviews, and other mutations. Identical concurrent reads share one upstream call, while overload fails quickly and truthfully as retryable HTTP 503 instead of cascading into route timeouts. ## Acceptance - Identical concurrent GETs execute once and return the same result to all callers. - Distinct reads never exceed the configured read capacity and saturated requests fail within the admission deadline. - Mutations are never coalesced and retain reserved capacity during read saturation. - Cancelling one GET waiter does not cancel work needed by other waiters. - Shutdown cancels shared requests before closing the HTTP client. - Configuration and retry behavior are documented; focused and full suites pass.
timmy was assigned by rockachopa 2026-08-08 00:28:36 +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#246
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?