Conversation
Drop "NetworkError when attempting to fetch resource" (Firefox) and "Failed to fetch" (Chrome/Safari) from Sentry reports. These are transient network errors caused by connectivity loss, DNS failures, or browser extensions — not actionable application bugs. Closes #8417 Closes #8388 Closes #8387 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Closes #8417
Closes #8388
Closes #8387
Summary
beforeSendhook to drop transient network fetch errorsNetworkError when attempting to fetch resourceand Chrome/Safari'sFailed to fetchTest plan
react-bootloader.tsxyarn test— 160 suites, 1550 tests passed)🤖 Generated with Claude Code