Skip to content

Add UnknownError with full response context for non-JSON API errors#196

Merged
mattrobenolt merged 1 commit intomainfrom
matt/unknown-error-context
Mar 23, 2026
Merged

Add UnknownError with full response context for non-JSON API errors#196
mattrobenolt merged 1 commit intomainfrom
matt/unknown-error-context

Conversation

@mattrobenolt
Copy link
Copy Markdown
Member

When an intermediary (e.g. Cloudflare Workers egress proxy) returns a
non-JSON response, capture HTTP status, headers, and body so the error
is diagnosable in Sentry without guesswork.

When an intermediary (e.g. Cloudflare Workers egress proxy) returns a
non-JSON response, capture HTTP status, headers, and body so the error
is diagnosable in Sentry without guesswork.
@mattrobenolt mattrobenolt force-pushed the matt/unknown-error-context branch from dc39727 to 041022e Compare March 23, 2026 20:22
@mattrobenolt mattrobenolt merged commit c915782 into main Mar 23, 2026
5 checks passed
@mattrobenolt mattrobenolt deleted the matt/unknown-error-context branch March 23, 2026 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants