Bound readiness probe latency #71

Closed
opened 2026-08-06 04:16:48 +00:00 by rockachopa · 0 comments
Member

Reproducible gap

GET /readyz directly awaits current_user() with no deadline. If Gitea accepts a connection but never responds, the readiness request remains pending indefinitely, unlike the bounded context and event endpoints.

Acceptance criteria

  • The Gitea readiness check has a deterministic timeout.
  • A timeout returns HTTP 503 with a retry hint and cancels the upstream task.
  • Existing readiness success and failure behavior remains covered.
## Reproducible gap `GET /readyz` directly awaits `current_user()` with no deadline. If Gitea accepts a connection but never responds, the readiness request remains pending indefinitely, unlike the bounded context and event endpoints. ## Acceptance criteria - The Gitea readiness check has a deterministic timeout. - A timeout returns HTTP 503 with a retry hint and cancels the upstream task. - Existing readiness success and failure behavior remains covered.
timmy was assigned by rockachopa 2026-08-06 04:16:48 +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#71
No description provided.