fix(orbital): Don't capture SSE parse errors to Sentry#18
Merged
rahulchhabria merged 1 commit intomasterfrom Mar 8, 2026
Merged
fix(orbital): Don't capture SSE parse errors to Sentry#18rahulchhabria merged 1 commit intomasterfrom
rahulchhabria merged 1 commit intomasterfrom
Conversation
Some browsers (notably Safari) merge adjacent SSE frames, producing unparseable data in onStreamMessage. These are transient network glitches with no actionable fix — log to console only to avoid false-positive Sentry alerts. Fixes ORBITAL-FRONTEND-1 Co-Authored-By: Claude <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.
Removes the
Sentry.captureExceptioncall from theonStreamMessageSSE parse error handler.Some browsers (notably Safari) occasionally merge adjacent SSE frames, producing unparseable payloads like
[50.1169data: [59.3287,18.0717,...,"javascript"]. These are transient network glitches with no actionable fix on our end — capturing them to Sentry just creates false-positive alerts (ORBITAL-FRONTEND-1).Console logging is kept so the issue remains visible during local debugging without polluting the error dashboard.
ORBITAL-FRONTEND-2 and ORBITAL-FRONTEND-3 are security researcher test events and should be manually resolved in Sentry — they're not caused by app code.
Fixes ORBITAL-FRONTEND-1