Skip to content

test(e2e): Look up events via the organization trace endpoint - #23371

Draft
chargome wants to merge 3 commits into
developfrom
test/e2e-send-to-sentry-trace-endpoint
Draft

test(e2e): Look up events via the organization trace endpoint#23371
chargome wants to merge 3 commits into
developfrom
test/e2e-send-to-sentry-trace-endpoint

Conversation

@chargome

Copy link
Copy Markdown
Member

GET /projects/{org}/{project}/events/{event_id}/ now 404s in the e2e org, so the two send-to-sentry apps look events up via GET /organizations/{org}/trace/{trace_id}/ instead — which is keyed by trace rather than event, so the apps now expose trace IDs alongside event IDs.

debug-id-sourcemaps stays on the old endpoint for now: it snapshots symbolicated stack frames, which the trace endpoint doesn't return.

`GET /projects/{org}/{project}/events/{event_id}/` now 404s in the e2e org, so the two
`send-to-sentry` apps look events up via `GET /organizations/{org}/trace/{trace_id}/`
instead - which is keyed by trace rather than event, so the apps now expose trace IDs
alongside event IDs.

`debug-id-sourcemaps` stays on the old endpoint for now: it snapshots symbolicated stack
frames, which the trace endpoint doesn't return.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@chargome chargome self-assigned this Aug 12, 2026
@github-actions

github-actions Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

size-limit report 📦

Path Size % Change Change
@sentry/browser 30.3 kB - -
@sentry/browser - with treeshaking flags 28.47 kB - -
@sentry/browser - with treeshaking flags tracing without tracing 26.81 kB - -
@sentry/browser (incl. Tracing) 48.54 kB - -
@sentry/browser (incl. Tracing + Span Streaming) 48.55 kB - -
@sentry/browser (incl. Tracing, Profiling) 51.43 kB - -
@sentry/browser (incl. Tracing, Replay) 87.94 kB - -
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 77.32 kB - -
@sentry/browser (incl. Tracing, Replay with Canvas) 92.67 kB - -
@sentry/browser (incl. Tracing, Replay, Feedback) 105.34 kB - -
@sentry/browser (incl. Feedback) 47.63 kB - -
@sentry/browser (incl. sendFeedback) 35.13 kB - -
@sentry/browser (incl. FeedbackAsync) 40.28 kB - -
@sentry/browser (incl. Metrics) 31.24 kB - -
@sentry/browser (incl. Logs) 31.52 kB - -
@sentry/browser (incl. Metrics & Logs) 32.15 kB - -
@sentry/react 32.09 kB - -
@sentry/react (incl. Tracing) 50.73 kB - -
@sentry/vue 35.31 kB - -
@sentry/vue (incl. Tracing) 50.5 kB - -
@sentry/svelte 30.33 kB - -
CDN Bundle 31.61 kB - -
CDN Bundle (incl. Tracing) 48.87 kB - -
CDN Bundle (incl. Logs, Metrics) 33.8 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) 50.79 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) 74.31 kB - -
CDN Bundle (incl. Tracing, Replay) 86.46 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) 88.29 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) 92.16 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) 94.11 kB - -
CDN Bundle - uncompressed 93.84 kB - -
CDN Bundle (incl. Tracing) - uncompressed 146.72 kB - -
CDN Bundle (incl. Logs, Metrics) - uncompressed 100.14 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed 152.41 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed 229.08 kB - -
CDN Bundle (incl. Tracing, Replay) - uncompressed 265.98 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed 271.65 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 279.68 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed 285.34 kB - -
@sentry/nextjs (client) 53.26 kB - -
@sentry/sveltekit (client) 48.96 kB - -
@sentry/core/server 65.34 kB - -
@sentry/core/browser 51.69 kB - -
@sentry/node 117.94 kB - -
@sentry/node/import (ESM hook with diagnostics-channel injection) 0 B added added
@sentry/node - without tracing 82.06 kB +0.01% +1 B 🔺
@sentry/aws-serverless 91.47 kB - -
@sentry/cloudflare (withSentry) - minified 214 kB - -
@sentry/cloudflare (withSentry) 528.8 kB - -

View base workflow run

chargome and others added 2 commits August 12, 2026 16:49
A rejected request and a trace that has not landed yet were indistinguishable, so a
permanently failing lookup presented as a polling timeout with no diagnostic.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
A 401/403 never resolves by polling, so surface it immediately rather than reporting it
as a missing event after the full timeout.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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