Show degraded status for fallback dashboard context #97

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

When /api/v1/context returns its HTTP 200 fallback payload with an error field, the dashboard currently sets the header status to Live · updated just now. This masks Gitea outages as healthy data. Reproduction: return {user: ..., repos: [], issues: [], pull_requests: [], deltas: [], error: "connection refused"} from the context request; the rendered status incorrectly says Live. Render an explicit degraded status while continuing to show the fallback context.

Acceptance: a behavioral frontend test covers the fallback payload and the rendered header does not claim Live.

When `/api/v1/context` returns its HTTP 200 fallback payload with an `error` field, the dashboard currently sets the header status to `Live · updated just now`. This masks Gitea outages as healthy data. Reproduction: return `{user: ..., repos: [], issues: [], pull_requests: [], deltas: [], error: "connection refused"}` from the context request; the rendered status incorrectly says Live. Render an explicit degraded status while continuing to show the fallback context. Acceptance: a behavioral frontend test covers the fallback payload and the rendered header does not claim Live.
timmy was assigned by rockachopa 2026-08-06 10:46:16 +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#97
No description provided.