Conversation
When Supabase returns HTML error pages (504 timeouts, CDN errors) instead of JSON, the storage client throws StorageUnknownError. Previously, even after retry attempts, these errors were sent to Sentry. Changes: - Mark persistent HTML errors as shouldBeCaptured: false in createSignedUrl - Preserve shouldBeCaptured flag when wrapping errors in refresh-main-image - Add specific error type for better debugging (persistent_html_error) - Ensure ShelfErrors are re-thrown as-is to preserve their flags This prevents transient Supabase infrastructure issues from spamming Sentry while still logging them for debugging and gracefully falling back to existing URLs. Fixes Sentry issue #7059127706
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When Supabase returns HTML error pages (504 timeouts, CDN errors) instead of JSON, the storage client throws StorageUnknownError. Previously, even after retry attempts, these errors were sent to Sentry.
Changes:
This prevents transient Supabase infrastructure issues from spamming Sentry while still logging them for debugging and gracefully falling back to existing URLs.
Fixes Sentry issue #7059127706