POR-22460: Filter cross-origin history SecurityError noise from Sentry - #1400
Draft
cursor[bot] wants to merge 2 commits into
Draft
POR-22460: Filter cross-origin history SecurityError noise from Sentry#1400cursor[bot] wants to merge 2 commits into
cursor[bot] wants to merge 2 commits into
Conversation
…1397) deleteLabel passed `id: currentLabel?.id` straight into label.delete, so when findFirst matched nothing Prisma got `{ id: undefined }` and threw PrismaClientValidationError, failing the whole delete transaction. Return early instead.
Add shared browser Sentry ignore patterns for history API instrumentation noise, including NS Pushstate prevention and cross-origin replaceState SecurityErrors seen during portal OAuth/login redirects. Co-authored-by: Neil Raina <makeitraina@users.noreply.github.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Greptile SummaryThis PR centralizes browser-side Sentry ignore patterns and adds filters for known cross-origin History API noise while preserving existing fetch-failure filtering.
Confidence Score: 5/5The PR appears safe to merge, with no concrete changed-code defect identified. The client configuration preserves the existing fetch filters, adds the intended browser History API noise patterns, and includes focused tests showing unrelated application errors remain reportable. Important Files Changed
Reviews (1): Last reviewed commit: "POR-22460: Filter cross-origin history S..." | Re-trigger Greptile |
Monfernape
approved these changes
Aug 21, 2026
SandipBajracharya
force-pushed
the
main
branch
from
August 26, 2026 13:11
1bc04dd to
51d44fd
Compare
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.
Changes
src/utils/sentryIgnoredErrors.tswith shared browser Sentry ignore patterns for history API instrumentation noiseNS Pushstate preventionand cross-originhistory.replaceState/history.pushStateSecurityErrormessages ininstrumentation-client.tssrc/utils/sentryIgnoredErrors.test.tsTesting Criteria
yarn test src/utils/sentryIgnoredErrors.test.ts— 4 tests passedNotes
SecurityError: Blocked attempt to use history.replaceState()during portal OAuth/login redirectsauth.copilot.appcallback), not a tasks-app business-logic failureNS Pushstate preventionwith the same patternImpact & Surface Area of Change