Skip to content

Filter browser fetch network errors in Sentry#1226

Draft
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/OUT-3740-automated-issue-triage-9fc4
Draft

Filter browser fetch network errors in Sentry#1226
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/OUT-3740-automated-issue-triage-9fc4

Conversation

@cursor
Copy link
Copy Markdown

@cursor cursor Bot commented May 14, 2026

Changes

  • Add browser-specific fetch transport errors to the Sentry client ignoreErrors list.
  • Preserve the existing fetch failed filter while covering Firefox's NetworkError when attempting to fetch resource. and Chrome-style Failed to fetch messages.

Testing Criteria

  • Ran yarn lint:check (passes with existing warnings).
  • Ran yarn tsc --noEmit (fails on existing missing SVG module declarations in src/icons/index.ts, unrelated to this change).

Notes

  • Linear: OUT-3740
  • Sentry: TASKS-85

Impact & Surface Area of Change

  • Client-side Sentry initialization only. The change suppresses known browser network transport failures from Sentry error ingestion and does not affect task API behavior or UI flows.
Open in Web View Automation 

Co-authored-by: Neil Raina <makeitraina@users.noreply.github.com>
@linear-code
Copy link
Copy Markdown

linear-code Bot commented May 14, 2026

OUT-3740

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 14, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tasks-app Ready Ready Preview, Comment May 14, 2026 10:23pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant