Skip to content

test(cloudflare): Port the vite-autoinstrument suites to span streaming - #24189

Draft
JPeer264 wants to merge 1 commit into
jp/cf-int-tests-propagation-streamingfrom
jp/cf-int-tests-vite-autoinstrument-streaming
Draft

JPeer264 wants to merge 1 commit into
jp/cf-int-tests-propagation-streamingfrom
jp/cf-int-tests-vite-autoinstrument-streaming

Conversation

@JPeer264

@JPeer264 JPeer264 commented Sep 8, 2026

Copy link
Copy Markdown
Member

Ports the seventeen suites/vite-autoinstrument suites off the traceLifecycle: 'static' pin.

Under streaming a whole request chain is one trace, so each suite reads the trace with collectStreamedSpans instead of one envelope expectation per hop. Every hop here (a Durable Object, a WorkerEntrypoint, a Workflow step) runs in its own isolate and streams its own envelope, so a single-envelope read would be a race.

The proof of instrumentation is unchanged, only its shape is: a Durable Object still shows the durable_object_storage_get / durable_object_storage_put pair, now as children of its own segment span rather than as spans of its transaction. The chain is asserted directly, a hop's segment span carries the previous hop's span_id as its parent_span_id, which is stronger than the disjointness the old unordered expectations relied on.

Every route in these suites is a raw URL, so the streamed segment name keeps the method only. GET /greet becomes GET, and the hop is identified through its url.path attribute. That matters for the entrypoint and combination suites, where the transaction name used to tell the hops apart.

The per-suite expectDurableObjectTransaction, expectMainWorkerTransaction and expectPlainTransaction helpers are gone. The assertions are inlined, and the suites that hit two endpoints loop over the two paths.

Part of #24148

🤖 Generated with Claude Code

@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

size-limit report 📦

Path Size % Change Change
@sentry/browser 29.09 kB - -
@sentry/browser - with treeshaking flags 27.35 kB - -
@sentry/browser - with treeshaking flags tracing without tracing 27.26 kB - -
@sentry/browser (incl. Tracing) 50.56 kB - -
@sentry/browser (incl. Tracing + Span Streaming) 50.58 kB - -
@sentry/browser (incl. Tracing, Profiling) 53.56 kB - -
@sentry/browser (incl. Tracing, Replay) 90.11 kB - -
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 79.21 kB - -
@sentry/browser (incl. Tracing, Replay with Canvas) 94.81 kB - -
@sentry/browser (incl. Tracing, Replay, Feedback) 107.78 kB - -
@sentry/browser (incl. Feedback) 46.62 kB - -
@sentry/browser (incl. sendFeedback) 34.15 kB - -
@sentry/browser (incl. FeedbackAsync) 39.26 kB - -
@sentry/browser (incl. Metrics) 30.1 kB - -
@sentry/browser (incl. Logs) 30.35 kB - -
@sentry/browser (incl. Metrics & Logs) 31.02 kB - -
@sentry/react 30.84 kB - -
@sentry/react (incl. Tracing) 52.88 kB - -
@sentry/vue 36.34 kB - -
@sentry/vue (incl. Tracing) 52.86 kB - -
@sentry/svelte 29.11 kB - -
CDN Bundle 30.8 kB - -
CDN Bundle (incl. Tracing) 51.1 kB - -
CDN Bundle (incl. Logs, Metrics) 33.06 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) 53.09 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) 73.75 kB - -
CDN Bundle (incl. Tracing, Replay) 88.66 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) 90.58 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) 94.7 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) 96.71 kB - -
CDN Bundle - uncompressed 91.16 kB - -
CDN Bundle (incl. Tracing) - uncompressed 152.53 kB - -
CDN Bundle (incl. Logs, Metrics) - uncompressed 97.73 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed 158.49 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed 227.14 kB - -
CDN Bundle (incl. Tracing, Replay) - uncompressed 272.1 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed 278.04 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 285.81 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed 291.74 kB - -
@sentry/nextjs (client) 55.21 kB - -
@sentry/sveltekit (client) 50.99 kB - -
@sentry/core/server 39.98 kB - -
@sentry/core/browser 13.66 kB - -
@sentry/node 133.34 kB +0.02% +25 B 🔺
@sentry/node/import (ESM hook with diagnostics-channel injection) 82.17 kB - -
@sentry/node - without tracing 89.93 kB +0.03% +21 B 🔺
@sentry/node - without channel injection 112.15 kB +0.02% +14 B 🔺
@sentry/aws-serverless 98.19 kB +0.02% +19 B 🔺
@sentry/cloudflare (withSentry) - minified 204.69 kB - -
@sentry/cloudflare (withSentry) 509.25 kB - -

View base workflow run

Removes the `traceLifecycle: 'static'` pin from the seventeen
`suites/vite-autoinstrument` suites, and rewrites the assertions from
transaction envelopes to span v2.

Under streaming a whole request chain is one trace, so a suite reads the trace
rather than one envelope per hop. Every suite now uses `collectStreamedSpans`,
because each hop, a Durable Object, a `WorkerEntrypoint` or a Workflow step,
runs in its own isolate and streams its own envelope.

The proof of instrumentation is unchanged, only its shape is. A Durable Object
still shows the `durable_object_storage_get` and `durable_object_storage_put`
pair, but as children of its own segment span rather than as `spans` of its
transaction. The chain is now asserted directly: a hop's segment span carries
the previous hop's `span_id` as its `parent_span_id`.

Every route in these suites is a raw URL, so the streamed segment name keeps the
method only. `GET /greet` becomes `GET`, and the hop is identified by its
`url.path` attribute. That matters for the entrypoint and combination suites,
where the segment name used to tell the hops apart.

The per-suite `expectDurableObjectTransaction`, `expectMainWorkerTransaction`
and `expectPlainTransaction` helpers are gone. The assertions are inlined, and
the suites that hit two endpoints loop over the two paths instead.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@JPeer264
JPeer264 force-pushed the jp/cf-int-tests-vite-autoinstrument-streaming branch from 6745f12 to 6d07153 Compare September 19, 2026 15:46
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