Hide upstream exception details from fallback context responses #111

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

Evidence: context() currently serializes str(e) for non-timeout upstream failures. A Gitea/network exception can therefore expose internal hostnames, request details, or other operational data through the public /api/v1/context response. Preserve explicit timeout messaging, but return a stable generic message for other upstream failures. Add a behavioral regression test.

Acceptance criteria:

  • Non-timeout upstream exception text is not included in the response.
  • The fallback response uses a stable actionable generic error.
  • Existing timeout behavior remains unchanged.
  • Full test suite passes.
Evidence: `context()` currently serializes `str(e)` for non-timeout upstream failures. A Gitea/network exception can therefore expose internal hostnames, request details, or other operational data through the public `/api/v1/context` response. Preserve explicit timeout messaging, but return a stable generic message for other upstream failures. Add a behavioral regression test. Acceptance criteria: - Non-timeout upstream exception text is not included in the response. - The fallback response uses a stable actionable generic error. - Existing timeout behavior remains unchanged. - Full test suite passes.
timmy was assigned by rockachopa 2026-08-06 14:16: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#111
No description provided.