Repository navigation
Filter confirmed injected browser errors from Sentry - #22
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
Browser-injected Firefox globals, MetaMask scripts and Facebook performance logging are reaching the transcripts Sentry project as application errors. Add a source-aware filter for their exact observed signatures, keeping mixed application stacks and exception chains visible.
The filter deliberately leaves
M_ID, unconfirmed native bridges, storage failures, media aborts and pipeline errors unchanged. Existing Kaltura filtering is unchanged. Replaying all 100 latest audit snapshots changes exactly 10 decisions; the other 90 retain their prior behavior. The Facebook signature with an SDK/application wrapper stays visible because ownership of every frame cannot be established.Validation: 22 focused regression cases; full suite 495 passed / 6 skipped; typecheck and focused ESLint passed. A production build passed before the final mixed-frame predicate tightening, which was then checked by the final typecheck and full suite. Independent code review found and verified the mixed-frame guard.