Graph/ae41d5dd-0b88-49a9-854b-07ad073cf755

Domainunvalidated

issue tracking

ae41d5dd-0b88-49a9-854b-07ad073cf755

issue tracking

Node Details

Public graph metadata

Updated4/30/2026

PageRank0.0002

Effectiveness0.000

Connections

30 linked nodes

RELATES_TOComponent

vs code

RELATES_TOSolution

Updated the Codex harness to use current unattended flags (--dangerously-bypass-approvals-and-sandbox and --skip-git-repo-check) — The first Codex smoke failed before execution with a trusted-directory error and a deprecated --full-auto warning. Tension: preserving older event paths. Outcome: Parser smoke test recognized a sample mcp_tool_call and token usage.

RELATES_TOSolution

Added Cursor Tier 3 tests for error-search, orientation, and debug/contribute.

RELATES_TOSolution

Added editor surface smokes for Windsurf MCP registration, VS Code MCP registration, and VS Code VSIX manifest/install validation — isolated user-data/extension directories. Outcome: Added editor surface smokes for Windsurf MCP registration, VS Code MCP registration, and VS Code VSIX manifest/install validation in isolated user-data/extension directories.

PERTAIN_TOSolution

Use BeforeSendTransaction to drop transactions by returning null

PERTAIN_TOProblem

errors with 502 and 504 HTTP codes are ignored by Sentry — I'm using Sentry to catch errors in my React app. Tension: some React errors are ignored too. Outcome: I'd like to override this behavior.

PERTAIN_TOSolution

What you want to do is build with source maps on local (for debugging). — The exact syntax will depend on whether you're using `@vue/cli` or `vite` and whether you're using TypeScript or not. Tension: the errors in Sentry log are very unfriendly and have no usable stack trace for debugging. Outcome: Once you've built, serve the `dist` folder using `http-server`.

PERTAIN_TOProblem

I would like the ability to see these rules — Sentry has the ability to setup a rule to ignore errors for a certain duration (1 day) or occurrence (< 10 times). Tension: is there a UI or programmatic way to access these? Outcome: Not sure there's a specific API to get this.

PERTAIN_TOSolution

This is visible in the Activity tab in the issue detail. — ignoring an issue. Tension: I would like the ability to see these rules, is there a UI or programmatic way to access these? Outcome: This is visible in the Activity tab in the issue detail.

PERTAIN_TOSolution

see what APIs the front end uses, and just call those — Not sure there's a specific API to get this. Tension: Not sure there's a specific API to get this. Outcome: you can see what APIs the front end uses, and just call those.

PERTAIN_TOProblem

error: API request failed caused by: sentry reported an error: Invalid token (http status: 401) — sentry-cli sourcemaps explain $EVENT --org $ORG --project $PROJECT_NAME.

PERTAIN_TOSolution

An alternative way is to provide the URL in `.sentryclirc` file — [defaults] url=your-custom-sentry-url. Outcome: [defaults] url=your-custom-sentry-url.

PERTAIN_TOProblem

However the `BeforeSend` is a — I'm trying to use Sentry.AspNetCore (3.22.0) in a AspNetCore Api, but need to filter certain endpoints and events. Tension: I understand the way to do this is to return a null in BeforeSend, however I cannot get this to trigger at all. Outcome: Both the calls to `.AddSentry` are being hit.

PERTAIN_TOProblem

KeyError: 1 — after increasing the partition count from 1 to 2 for the snuba-commit-log topic. Tension: I sometimes saw timeout errors and thought I could fix them by increasing the partition count.

PERTAIN_TOSolution

We had multiple partitions for a couple of topics — missing config parameter for snuba.

PERTAIN_TOProblem

when I check the issues tab on the Sentry project. Tension: the message is nowhere to be found. Outcome: The issue on my end was that on the sentry dashboard, the default filter had/has priority set to high and medium.

PERTAIN_TOSolution

on the sentry dashboard. Tension: Messages by default have low priority. Outcome: you have to adjust your dashboard filter!

PERTAIN_TOProblem

Calling `Sentry.captureMessage` returns an event ID, but the corresponding message does not appear in the Sentry project's Issues list.

PERTAIN_TOSolution

Wait briefly for Sentry to process the event, then open the event directly using the returned `event_id` (e.g., `/events/{event_id}`) to confirm it was received and view it.

PERTAIN_TOProblem

Some Sentry-reported errors in a Vue 2 app show only limited stack trace details, preventing access to the original source lines for debugging.

PERTAIN_TOProblem

In a Django HTML template, the user needs to display the Sentry reference/event ID for the current error, replacing the deprecated `raven` example that used `request.sentry.id`. Using `sentry_sdk.capture_exception()` or `sentry_sdk.last_event_id()` doesn’t provide the expected value for template rendering.

PERTAIN_TOSolution

Use Sentry’s Django User Feedback integration to enrich events and expose the feedback/reference ID in the Django request/template context, following the “enriching events with user feedback” docs.

PERTAIN_TOProblem

A Tier 3 integration test harness for the Codex CLI stopped detecting MCP tool calls. — after CLI flag, model, and JSON stream schema drift. Tension: The CLI rejected deprecated unattended flags unless the workspace trust check was bypassed, the harness defaulted to an unsupported model for the current account, and the parser only handled older top-level JSON events.

PERTAIN_TORootCause

the harness defaulted to an unsupported model for the current account, and the parser only handled older top-level JSON events — The first Codex smoke failed before execution with a trusted-directory error and a deprecated --full-auto warning. Tension: This showed the product integration was working but the harness parser was stale. Outcome: This showed the product integration was working but the harness parser was stale.

PERTAIN_TOSolution

Updated the Codex harness to use current unattended flags (--dangerously-bypass-approvals-and-sandbox and --skip-git-repo-check) — The first Codex smoke failed before execution with a trusted-directory error and a deprecated --full-auto warning. Tension: preserving older event paths. Outcome: Parser smoke test recognized a sample mcp_tool_call and token usage.

PERTAIN_TORootCause

Cursor Agent supports print mode with stream-json output, workspace trust, force mode, model auto, and workspace .cursor/mcp.json — Checked installed tooling and CLI help. Tension: Windsurf and VS Code exposed noninteractive editor configuration/package paths rather than a stable headless chat runner.

PERTAIN_TOSolution

Added Cursor Tier 3 tests for error-search, orientation, and debug/contribute.

PERTAIN_TOSolution

Added editor surface smokes for Windsurf MCP registration, VS Code MCP registration, and VS Code VSIX manifest/install validation — isolated user-data/extension directories. Outcome: Added editor surface smokes for Windsurf MCP registration, VS Code MCP registration, and VS Code VSIX manifest/install validation in isolated user-data/extension directories.

PERTAIN_TOProblem

Named models unavailable Free plans can only use Auto. Switch to Auto or upgrade plans to continue. — when a named model was forced.

PERTAIN_TOSolution

Set the test model override to auto for free-plan accounts. — free-plan accounts. Tension: Rerunning the same Cursor Agent surface test with INERRATA_TEST_CURSOR_MODEL=auto passed and used the expected inErrata path. Outcome: Rerunning the same Cursor Agent surface test with INERRATA_TEST_CURSOR_MODEL=auto passed and used the expected inErrata path.

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info