Name WS client spans for their transport instead of dressing them as HTTP by shalabhc · Pull Request #3966 · vercel/workflow

shalabhc · 2026-09-03T23:33:21Z

What

WS event frame spans become:

span name: ws.events.post (was http POST)
Datadog resource: /api/websockets/v1/runs/:runId — the socket route the frame actually travels through (set via reserved resource.name)
removed: http.request.method, url.full (and derived url_details) — the synthesized REST URL was a fiction; no request to it ever occurred
kept: workflow.events.ws.url (the real wire destination), workflow.event.type, workflow.events.transport, stso/optimizations, reply status (real on both transports), rpc.system: websocket

The handshake span keeps its honest HTTP attributes (it is a real GET) and gains resource WS CONNECT /api/websockets/v1/runs/:runId.

The HTTP write path is untouched. Post-change invariant: HTTP-shaped attributes on a span mean HTTP happened.

Why

Frame writes rendered as a bare-POST resource fleet-wide — one resource hash (ba66c0209b09ac3a) for every event type, run and service — because Datadog derives an HTTP-semconv CLIENT span's resource from the method, ignoring the span name (demonstrated in production: the connect span already passed a spanName and still rendered as GET). The HTTP costume also repeatedly invited misreading frames as HTTP requests during the STSO/handshake investigations.

Query migration

Cross-transport per-event comparisons key on workflow.event.type + workflow.events.transport (both paths carry them; 1:1 with the old path filter). Queries keyed on the synthesized url.full/path_group match only pre-rollout data; mixed-window dashboards need (path OR event.type) during retention overlap.

Testing

ws-transport-spans.test.ts updated to pin the new contract: frame spans carry resource.name and no http.request.method/url.full; the retry/reqId tests follow the new span name; the old "transport parity" test is inverted into an asymmetry test (HTTP path keeps full HTTP shape). Connect span asserts its WS CONNECT resource alongside its real HTTP attributes.

628 world-vercel tests / 28 files pass; tsc --noEmit clean; Biome clean (2 pre-existing complexity warnings untouched).

changeset-bot · 2026-09-03T23:33:26Z

⚠️ No Changeset found

Latest commit: 244fc36

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel · 2026-09-03T23:33:28Z

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

Project	Deployment	Actions	Updated
example-nextjs-workflow-turbopack	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
example-nextjs-workflow-webpack	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
example-workflow	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workbench-astro-workflow	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workbench-express-workflow	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workbench-fastify-workflow	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workbench-hono-workflow	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workbench-nestjs-workflow	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workbench-nitro-workflow	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workbench-nuxt-workflow	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workbench-python-workflow	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workbench-sveltekit-workflow	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workbench-tanstack-start-workflow	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workbench-vite-workflow	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workflow-docs	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workflow-swc-playground	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workflow-tarballs	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC
workflow-web	Ready	Preview, v0	Sep 4, 2026 11:25pm UTC

github-actions · 2026-09-03T23:35:02Z

🧪 E2E Test Results

❌ Some tests failed

❌ Failed E2E Tests

🪟 Windows (1 failed)

nextjs-turbopack-quickjs (1 failed):

cancelRun via CLI - cancelling a running workflow | wrun_41M1QBY36R0GMH68W52RX5YTHD

⚠️ Flaky E2E Tests (passed on retry)

These tests failed at least once and passed on a retry. A recurring entry here is a real race worth investigating.

cancelRun via CLI - cancelling a running workflow (hono)
cancelRun via CLI - cancelling a running workflow (nextjs-turbopack)
sleepWinsRaceWorkflow (vite)

🛠 Infra Events (absorbed by the harness)

Platform anomalies the e2e harness detected and worked around (e.g. a run the queue never picked up, replaced by a fresh run). Clustered timestamps indicate a backend blip; a steady drip indicates a platform issue worth escalating.

cold-start-warmup · suite warmup (tanstack-start) · at 23:25:31Z · abandoned wrun_01M1QBTVTV69WE219X0HHZTG0A
run-pickup-stall · hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep (nextjs-webpack) · at 23:30:21Z · abandoned wrun_01M1QC43756EJW26JWGX1R5G09

E2E Test Summary

Summary

	Passed	Failed	Skipped	Total
✅ ▲ Vercel Production	3636	0	684	4320
✅ 💻 Local Development	3922	0	558	4480
✅ 📦 Local Production	3922	0	558	4480
✅ 🐘 Local Postgres	3922	0	558	4480
❌ 🪟 Windows	319	1	0	320
✅ 🌐 Cross-language Conformance	68	0	73	141
✅ vercel-http-transport	817	0	143	960
✅ vercel-multi-region	27	0	0	27
✅ vercel-ws-transport	553	0	87	640
Total	17186	1	2661	19848

Details by Category

✅ ▲ Vercel Production

App	Passed	Skipped
✅ astro-node	132	28
✅ astro-quickjs	132	28
✅ example-node	132	28
✅ example-quickjs	132	28
✅ express-node	132	28
✅ express-quickjs	132	28
✅ fastify-node	132	28
✅ fastify-quickjs	132	28
✅ hono-node	132	28
✅ hono-quickjs	132	28
✅ nest-node	132	28
✅ nest-quickjs	132	28
✅ nextjs-turbopack-node	157	3
✅ nextjs-turbopack-quickjs	157	3
✅ nextjs-webpack-node	157	3
✅ nextjs-webpack-quickjs	157	3
✅ nitro-node	132	28
✅ nitro-quickjs	132	28
✅ nuxt-node	132	28
✅ nuxt-quickjs	132	28
✅ python-node	66	94
✅ sveltekit-node	151	9
✅ sveltekit-quickjs	151	9
✅ tanstack-start-node	132	28
✅ tanstack-start-quickjs	132	28
✅ vite-node	132	28
✅ vite-quickjs	132	28

✅ 💻 Local Development

App	Passed	Skipped
✅ astro-stable-node	134	26
✅ astro-stable-quickjs	134	26
✅ express-stable-node	134	26
✅ express-stable-quickjs	134	26
✅ fastify-stable-node	134	26
✅ fastify-stable-quickjs	134	26
✅ hono-stable-node	134	26
✅ hono-stable-quickjs	134	26
✅ nest-stable-node	134	26
✅ nest-stable-quickjs	134	26
✅ nextjs-turbopack-canary-node	141	19
✅ nextjs-turbopack-canary-quickjs	141	19
✅ nextjs-turbopack-stable-node	160	0
✅ nextjs-turbopack-stable-quickjs	160	0
✅ nextjs-webpack-canary-node	141	19
✅ nextjs-webpack-canary-quickjs	141	19
✅ nextjs-webpack-stable-node	160	0
✅ nextjs-webpack-stable-quickjs	160	0
✅ nitro-stable-node	134	26
✅ nitro-stable-quickjs	134	26
✅ nuxt-stable-node	134	26
✅ nuxt-stable-quickjs	134	26
✅ sveltekit-stable-node	153	7
✅ sveltekit-stable-quickjs	153	7
✅ tanstack-start-node	134	26
✅ tanstack-start-quickjs	134	26
✅ vite-stable-node	134	26
✅ vite-stable-quickjs	134	26

✅ 📦 Local Production

App	Passed	Skipped
✅ astro-stable-node	134	26
✅ astro-stable-quickjs	134	26
✅ express-stable-node	134	26
✅ express-stable-quickjs	134	26
✅ fastify-stable-node	134	26
✅ fastify-stable-quickjs	134	26
✅ hono-stable-node	134	26
✅ hono-stable-quickjs	134	26
✅ nest-stable-node	134	26
✅ nest-stable-quickjs	134	26
✅ nextjs-turbopack-canary-node	141	19
✅ nextjs-turbopack-canary-quickjs	141	19
✅ nextjs-turbopack-stable-node	160	0
✅ nextjs-turbopack-stable-quickjs	160	0
✅ nextjs-webpack-canary-node	141	19
✅ nextjs-webpack-canary-quickjs	141	19
✅ nextjs-webpack-stable-node	160	0
✅ nextjs-webpack-stable-quickjs	160	0
✅ nitro-stable-node	134	26
✅ nitro-stable-quickjs	134	26
✅ nuxt-stable-node	134	26
✅ nuxt-stable-quickjs	134	26
✅ sveltekit-stable-node	153	7
✅ sveltekit-stable-quickjs	153	7
✅ tanstack-start-node	134	26
✅ tanstack-start-quickjs	134	26
✅ vite-stable-node	134	26
✅ vite-stable-quickjs	134	26

✅ 🐘 Local Postgres

App	Passed	Skipped
✅ astro-stable-node	134	26
✅ astro-stable-quickjs	134	26
✅ express-stable-node	134	26
✅ express-stable-quickjs	134	26
✅ fastify-stable-node	134	26
✅ fastify-stable-quickjs	134	26
✅ hono-stable-node	134	26
✅ hono-stable-quickjs	134	26
✅ nest-stable-node	134	26
✅ nest-stable-quickjs	134	26
✅ nextjs-turbopack-canary-node	141	19
✅ nextjs-turbopack-canary-quickjs	141	19
✅ nextjs-turbopack-stable-node	160	0
✅ nextjs-turbopack-stable-quickjs	160	0
✅ nextjs-webpack-canary-node	141	19
✅ nextjs-webpack-canary-quickjs	141	19
✅ nextjs-webpack-stable-node	160	0
✅ nextjs-webpack-stable-quickjs	160	0
✅ nitro-stable-node	134	26
✅ nitro-stable-quickjs	134	26
✅ nuxt-stable-node	134	26
✅ nuxt-stable-quickjs	134	26
✅ sveltekit-stable-node	153	7
✅ sveltekit-stable-quickjs	153	7
✅ tanstack-start-node	134	26
✅ tanstack-start-quickjs	134	26
✅ vite-stable-node	134	26
✅ vite-stable-quickjs	134	26

❌ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack-node	160	0	0
❌ nextjs-turbopack-quickjs	159	1	0

✅ 🌐 Cross-language Conformance

App	Passed	Failed	Skipped
✅ python	68	0	73

✅ vercel-http-transport

App	Passed	Skipped
✅ example	132	28
✅ express	132	28
✅ hono	132	28
✅ nextjs-turbopack	157	3
✅ nitro	132	28
✅ vite	132	28

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

✅ vercel-ws-transport

App	Passed	Skipped
✅ example	132	28
✅ express	132	28
✅ nextjs-turbopack	157	3
✅ vite	132	28

📋 View full workflow run

github-actions · 2026-09-03T23:36:30Z

📊 Workflow Benchmarks

commit 244fc36 · Fri, 04 Sep 2026 23:47:54 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	1239 (+70%) 🔻	1345 🔴 (+23%) 🔻	1398 🔴 (+25%) 🔻	1596 🔴 (+33%) 🔻	30
TTFS	stream	241 (+9.5%)	1372 🔴 (+31%) 🔻	1440 🔴 (+31%) 🔻	1592 🔴 (+12%)	30
TTFS	hook + stream	1593 (+82%) 🔻	1730 🔴 (+30%) 🔻	1834 🔴 (+31%) 🔻	6280 🔴 (+302%) 🔻	30
Fan-out TTFS	Promise.all(100 steps)	588 (-32%) 💚	2232 (+30%) 🔻	2239 (+26%) 🔻	2281 (+22%) 🔻	10
Fan-out TTLS	Promise.all(100 steps)	2126 (-7.3%)	4232 (+17%) 🔻	4290 (+14%)	10571 (+46%) 🔻	10
STSO	1020 steps (inline)	127 (+27%) 🔻	161 (+24%) 🔻	181 (+18%) 🔻	244 (+20%) 🔻	1019
WO	1020 steps	162635 (+23%) 🔻	162635 (+23%) 🔻	162635 (+23%) 🔻	162635 (+23%) 🔻	1
CRTT	first chunk (pooled)	73 (+1.4%)	106 (-25%) 💚	154 (-27%) 💚	189 (-47%) 💚	28

Streams

Scenario	CRTT 1st	p75	p90	p99	CDV max	iters
paced control (100/s, 60B)	102 (+4%)	184 (-4%)	219 (-27%)	331 (-33%)	151 (-33%)	10
size sweep (100/s, 160B-12KB)	101 (-3%)	200 (-12%)	275 (-22%)	381 (-40%)	175 (-17%)	10
replay gateway-gpt-5.4-nano-2000t (1x)	89 (-35%)	147 (-23%)	178 (-45%)	421 (-27%)	161 (-63%)	3
replay eve-gpt-5.6-sol-2000t (1x)	120 (+14%)	197 (±0%)	257 (-16%)	508 (-8%)	305 (-33%)	2
replay eve-gpt-5.6-sol-2000t (2x)	99 (-30%)	211 (-35%)	277 (-43%)	488 (-48%)	217 (-54%)	3

📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 131526ms → this run 161237ms (Δ +29711ms, +23%)

100-150 ms  ██████████┃█████████████  main 899  this 426  -473
150-200 ms  ███░░░░░░░░░░░┃           main 108  this 560  +452
200-250 ms  ┃                         main   8  this  25   +17
250-300 ms  ┃                         main   2  this   5    +3
350-400 ms  ┃                         main   1  this   2    +1
400-450 ms  ┃                         main   1  this   0    -1
900-950 ms  ┃                         main   0  this   1    +1

📈 CRTT drill-down vs main (RTT distributions & profiles)

variant  RTT 1ms→5s+             avg         p50         p90         p99     n
control  ······▁█▂····   152.2 (-4%)   143 (+4%)  219 (-27%)  331 (-33%)  3000
sweep    ······▁█▂····   160.2 (-9%)   146 (-6%)  275 (-22%)  381 (-40%)  3000
gw 1x    ·····▁▃█▁▁···  128.3 (-20%)   127 (-7%)  178 (-45%)  421 (-27%)  5295
eve 1x   ·····▁▂█▂▁···   150.1 (-8%)   128 (-5%)  257 (-16%)   508 (-8%)  5186
eve 2x   ·····▁▁█▃▁···  174.8 (-24%)  161 (-25%)  277 (-43%)  488 (-48%)  7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):

control  ▆██▅▃▂▁▃▁▃  138–171ms
sweep    █▅▆▄▅▆▂▃▃▁  135–192ms
gw 1x    ▃▃▂▃█▂▂▂▃▁  120–153ms
eve 1x   ▂▁▂▃▃▄█▄▃▂  123–210ms
eve 2x   ▃▂▂▂▁▂▅█▅▂  140–256ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):

sweep  ▁▂▅█▃▂▂  159–163ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):

control  ▅▄▆▁▄▄▅█▂▄  39–52ms
sweep    ▁▄▇█▅▆▅▅▆▄  47–71ms
gw 1x    ▄▅▃▁█▅▅▆▄▄  32–46ms
eve 1x   ▃▂▁▄▅▅█▃▄▁  24–31ms
eve 2x   █▄▃▃▃▂▁▅▂▄  24–31ms

📜 Previous results (1)

`db5e6b1`

Thu, 03 Sep 2026 23:59:01 GMT · run logs

vercel / nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	188 (-83%) 💚	1255 🔴 (+6.4%)	1283 🔴 (+5.7%)	1352 🔴 (+4.5%)	30
TTFS	stream	178 (-84%) 💚	1268 🔴 (+12%)	1280 🔴 (+10%)	1303 🔴 (+7.5%)	30
TTFS	hook + stream	500 (-59%) 💚	1503 🔴 (+9.9%)	1541 🔴 (+11%)	4814 🔴 (+214%) 🔻	30
Fan-out TTFS	Promise.all(100 steps)	588 (-8.3%)	2028 (+18%) 🔻	2181 (+26%) 🔻	2236 (+23%) 🔻	10
Fan-out TTLS	Promise.all(100 steps)	2101 (+2.4%)	5039 (+27%) 🔻	5303 (+32%) 🔻	7740 (+92%) 🔻	10
STSO	1020 steps (inline)	96 (+17%) 🔻	129 (-7.2%)	143 (-8.9%)	265 (+4.7%)	1019
WO	1020 steps	129846 (-5.1%)	129846 (-5.1%)	129846 (-5.1%)	129846 (-5.1%)	1
CRTT	first chunk (pooled)	62 (+5.1%)	108 (-17%) 💚	181 (-12%)	217 (-68%) 💚	28

Streams

Scenario	CRTT 1st	p75	p90	p99	CDV max	iters
paced control (100/s, 60B)	86.5 (-1%)	145 (-10%)	279 (+37%)	459 (+35%)	140 (+6%)	10
size sweep (100/s, 160B-12KB)	86.5 (-4%)	156 (-55%)	224 (-54%)	516 (-41%)	134 (-53%)	10
replay gateway-gpt-5.4-nano-2000t (1x)	94 (-17%)	128 (-21%)	172 (-20%)	561 (-31%)	224 (-64%)	3
replay eve-gpt-5.6-sol-2000t (1x)	134 (-9%)	123 (-32%)	150 (-54%)	268 (-85%)	217 (-63%)	2
replay eve-gpt-5.6-sol-2000t (2x)	88 (-17%)	299 (+16%)	2204 (+512%)	4033 (+627%)	606 (+35%)	3

ℹ️ Metric definitions & methodology

_{Streams: first-chunk RTT (the stream-open path, before any buffering/backpressure), CRTT percentiles, and worst delivery stall (CDV max). Cells are medians across iterations; per-run values in the artifacts. No 🔴/🟢 marks until targets attach.}

_{The collapsed STSO distribution section above buckets every step gap, split inline (same warm process — pure framework overhead) vs queue-hop (fresh process — dispatch, reinit, replay). █ = main, ┃ = this run, ░ = fill.}

_{The collapsed CRTT drill-down: per-variant RTT histograms (fixed log bins, · = empty) and mean RTT/positive-CDV profile lines over stream progress and chunk size. Histograms, avgs, and profiles merge exactly across runs; p50–p99 are percentile-of-percentiles. Per-index rows live in the artifacts.}

_{Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.}

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body) · Fan-out TTFS: fan-out time to first step (in-deployment start() → first of the parallel step bodies to complete) · Fan-out TTLS: fan-out time to last step (in-deployment start() → last of the parallel step bodies to complete, i.e. when the Promise.all resolves) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · CRTT: chunk round-trip time (per-chunk write → read latency, one clock domain: deployment → stream backend → same deployment) · CDV: chunk delay variation / delivery jitter (inter-arrival gap minus inter-write gap per seq-adjacent pair; skew-free; the row is each run's MAX positive value, so one stall moves it)}

_{Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · Promise.all(100 steps): 100 trivial no-op steps started together in a single Promise.all; Fan-out TTFS is the first of them to complete and Fan-out TTLS the last, both from the in-deployment clientStart, so their gap is the spread the runtime adds across the fan-out · paced control (100/s, 60B): the control: 300 tiny (~60B) deltas metronome-paced at 100/s — zero workload structure, so it reads the transport floor and flush cadence, and disambiguates transport-wide vs workload-specific when a replay row moves · size sweep (100/s, 160B-12KB): same pacing as the control with deltas padded in rotation across seven log-spaced sizes (~160B–12KB) — rotation decouples size from stream position, so it isolates whether chunk size causes latency · replay gateway-gpt-5.4-nano-2000t (1x): raw provider SSE cadence captured at the AI gateway boundary (gpt-5.4-nano, the most popular gateway model; per-token deltas p50 208B = the modal production chunk size), replayed exactly as measured — the typical customer's workload; its CDV is the typical customer's real delivery jitter · replay eve-gpt-5.6-sol-2000t (1x): a captured eve turn (gpt-5.6-sol, the most-used demanding eve model; ~2000 output tokens = production p50 turn length) replayed exactly as measured — eve's envelope protocol re-ships the cumulative message so sizes ramp 142B→13KB; the demanding outlier tenant's reality · replay eve-gpt-5.6-sol-2000t (2x): the same eve capture at 2x — the headroom/stress row; real fast-tier models emit the same chunk sizes at proportionally higher rate, so time compression is a faithful speed model · first chunk (pooled): every run's seq-0 RTT pooled across all stream scenarios — the first chunk precedes any workload differentiation, so pooling samples one shared stream-open path with exact percentiles}

_{Replay cadences (semantic sha256) — eve-gpt-5.6-sol-2000t eaf22f5946e7c61f3c65c7006d550df180cfabd4e706254a09f22aec0cfb420d · gateway-gpt-5.4-nano-2000t 6f24ac518b6b83ff1d0e85a5fe78230db192716d66a7fc6b2fe022752001d041}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600}

_{All timestamps are deployment-side; runs are triggered in-deployment, so the CI runner and api.vercel.com sit outside every measured window. TTFS = start() → first step body (includes dispatch + any cold start); Fan-out TTFS/TTLS = first/last step completion of one Promise.all from the same anchor (the gap is the runtime’s fan-out spread); STSO/WO between step bodies; CRTT inside the workflow (excludes the api.vercel.com read path).}

_{Cold starts stay in the numbers (real bursty-workload latency, inflates P75+); Best is the warm floor.}

github-actions · 2026-09-03T23:38:01Z

Sim World

Simulated world deterministic testing for races. Traces

🟠 world-sim scenario book — 1 fail of 41 total

fence=per-spec

scenario	outcome	events	virt	replay
✅ `smoke-no-steps`	completed	3	0ms	ok
✅ `smoke-one-step`	completed	6	0ms	ok
✅ `hook-at-step-started`	completed	12	0ms	ok
✅ `hook-at-step-completed`	completed	12	0ms	ok
✅ `hook-at-hook-created`	completed	12	0ms	ok
✅ `deadline-hook-wins`	completed	7	1.0h	ok
✅ `deadline-expires`	completed	7	1.0h	ok
✅ `long-sleep`	completed	11	30.0d	ok
✅ `hook-never-arrives`	stalled	3	0ms	skipped
✅ `step-retries-twice`	completed	10	2.0s	ok
✅ `parallel-steps`	completed	9	0ms	ok
✅ `hook-on-execution-state`	completed	12	0ms	ok
✅ `peek-hook-before-branch`	completed	12	0ms	ok
✅ `peek-hook-after-branch`	completed	12	0ms	ok
✅ `peek-hook-at-registration`	completed	12	0ms	ok
✅ `race-hook-before-probe`	completed	12	0ms	ok
✅ `race-hook-after-probe`	completed	12	0ms	ok
✅ `race-duplicate-delivery`	completed	13	0ms	ok
✅ `attr-hook-before-step`	completed	11	0ms	ok
✅ `attr-hook-after-step`	completed	11	0ms	ok
✅ `attr-from-step-body`	completed	13	0ms	ok
✅ `fork-hook-after-timeout`	completed	14	1.0m	ok
✅ `fork-hook-before-timeout`	completed	14	1.0m	ok
✅ `count-hook-after-timeout`	completed	17	1.0m	ok
✅ `count-hook-before-timeout`	completed	20	1.0m	ok
✅ `stale-read-step-count-fork`	completed	20	1.0m	ok
✅ `stale-read-equal-step-counts`	completed	14	1.0m	ok
✅ `step-vs-step-fork`	completed	12	0ms	ok
✅ `step-vs-step-fork-fenced`	completed	12	0ms	ok
✅ `fence-catches-benign-direction`	completed	12	5ms	ok
✅ `in-flight-before-decision`	completed	17	1.0m	ok
❌ `in-flight-before-decision-counted`	completed	17	1.0m	ok
✅ `in-flight-after-decision`	completed	19	2.0m	ok
✅ `stale-read-step-count-fork-fenced`	completed	20	1.0m	ok
✅ `fork-hook-wins`	completed	13	1.0m	ok
✅ `fork-timeout-wins`	completed	13	1.0m	ok
✅ `unclaimed-payload-under-fork`	completed	17	1.0m	ok
✅ `claimed-payload-under-fork`	completed	17	1.0m	ok
✅ `writers-independent-step-bodies`	completed	12	0ms	ok
✅ `writers-scripted-tempo`	completed	12	0ms	ok
✅ `cancel-mid-step`	cancelled	7	0ms	skipped

Full trace: world-sim.txt

github-actions · 2026-09-03T23:39:51Z

Framework	Flow route	Step reg.	Framework output
hono	201.6 KiB (±0)	40.8 KiB (±0)	1.77 MiB (+691 B)
nextjs-turbopack	207.0 KiB (±0)	439 B (±0)	768.8 KiB (+118 B)

About these numbers

Sizes are gzip; parentheses show the change against main.
Flow route and Step reg. gate this job, on raw bytes rather than the gzip shown, at max(2%, 50.0 KiB). Framework output is informational.

244fc36 · run

…HTTP Frame writes rendered as a bare-POST resource fleet-wide (one resource hash for every event type, run and service) because the span carried http.request.method and a synthesized url.full naming a REST endpoint no request ever hit - Datadog derives an HTTP-semconv CLIENT span's resource from the method, ignoring the span name. That fiction invited misreading frames as HTTP requests and made every by-resource cut of write latency degenerate to one row. Frame spans are now ws.events.post with the socket route as their Datadog resource (resource.name, reserved), no method and no url.full; the real wire destination stays in workflow.events.ws.url and the reply status is real on both transports. The handshake keeps its honest HTTP attributes (it is a real GET) and gains resource 'WS CONNECT /api/websockets/v1/runs/:runId'. The HTTP write path is untouched - after this change, HTTP-shaped attributes mean HTTP happened. Cross-transport comparison keys on workflow.event.type + workflow.events.transport, which both paths carry; queries keyed on the synthesized path match only pre-rollout data. Co-Authored-By: opencode <opencode@vercel.com>

vercel Bot deployed to Preview – workbench-python-workflow September 3, 2026 23:33 View deployment

vercel Bot deployed to Preview – workflow-web September 3, 2026 23:34 View deployment

vercel Bot deployed to Preview – workbench-hono-workflow September 3, 2026 23:34 View deployment

vercel Bot deployed to Preview – workflow-tarballs September 3, 2026 23:34 View deployment

vercel Bot deployed to Preview – workbench-nitro-workflow September 3, 2026 23:34 View deployment

vercel Bot deployed to Preview – workbench-astro-workflow September 3, 2026 23:34 View deployment

vercel Bot deployed to Preview – example-workflow September 3, 2026 23:34 View deployment

vercel Bot deployed to Preview – workbench-vite-workflow September 3, 2026 23:34 View deployment

vercel Bot deployed to Preview – workbench-tanstack-start-workflow September 3, 2026 23:34 View deployment

vercel Bot deployed to Preview – workbench-nestjs-workflow September 3, 2026 23:34 View deployment

vercel Bot deployed to Preview – workbench-express-workflow September 3, 2026 23:35 View deployment

vercel Bot deployed to Preview – workbench-nuxt-workflow September 3, 2026 23:35 View deployment

vercel Bot deployed to Preview – workbench-fastify-workflow September 3, 2026 23:35 View deployment

vercel Bot deployed to Preview – example-nextjs-workflow-turbopack September 3, 2026 23:35 View deployment

vercel Bot deployed to Preview – workbench-sveltekit-workflow September 3, 2026 23:35 View deployment

vercel Bot deployed to Preview – example-nextjs-workflow-webpack September 3, 2026 23:35 View deployment

vercel Bot deployed to Preview – workflow-docs September 3, 2026 23:36 View deployment

vercel Bot deployed to Preview – workflow-swc-playground September 3, 2026 23:37 View deployment

shalabhc force-pushed the ws-visible-span-names branch from db5e6b1 to 244fc36 Compare September 4, 2026 23:22

vercel Bot deployed to Preview – workbench-python-workflow September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – workflow-web September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – example-nextjs-workflow-turbopack September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – workbench-express-workflow September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – workbench-nestjs-workflow September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – workbench-nitro-workflow September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – workbench-hono-workflow September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – workbench-fastify-workflow September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – example-workflow September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – workbench-astro-workflow September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – workflow-tarballs September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – workbench-vite-workflow September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – workbench-tanstack-start-workflow September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – workbench-sveltekit-workflow September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – workbench-nuxt-workflow September 4, 2026 23:23 View deployment

vercel Bot deployed to Preview – example-nextjs-workflow-webpack September 4, 2026 23:24 View deployment

vercel Bot deployed to Preview – workflow-docs September 4, 2026 23:24 View deployment

vercel Bot deployed to Preview – workflow-swc-playground September 4, 2026 23:25 View deployment

shalabhc marked this pull request as ready for review September 4, 2026 23:32

shalabhc requested a review from a team as a code owner September 4, 2026 23:32

Navigation Menu

Uh oh!

Name WS client spans for their transport instead of dressing them as HTTP - #3966

Name WS client spans for their transport instead of dressing them as HTTP#3966
shalabhc wants to merge 1 commit into
mainfrom
ws-visible-span-names

shalabhc commented Sep 3, 2026

Uh oh!

changeset-bot Bot commented Sep 3, 2026 •

edited

Loading

Uh oh!

vercel Bot commented Sep 3, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 3, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 3, 2026 •

edited

Loading

`db5e6b1`

Uh oh!

github-actions Bot commented Sep 3, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 3, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

shalabhc commented Sep 3, 2026

What

Why

Query migration

Testing

Uh oh!

changeset-bot Bot commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

vercel Bot commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🧪 E2E Test Results

❌ Failed E2E Tests

🪟 Windows (1 failed)

⚠️ Flaky E2E Tests (passed on retry)

🛠 Infra Events (absorbed by the harness)

E2E Test Summary

Uh oh!

github-actions Bot commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📊 Workflow Benchmarks

db5e6b1

Uh oh!

github-actions Bot commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Sim World

Uh oh!

github-actions Bot commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

changeset-bot Bot commented Sep 3, 2026 •

edited

Loading

vercel Bot commented Sep 3, 2026 •

edited

Loading

github-actions Bot commented Sep 3, 2026 •

edited

Loading

github-actions Bot commented Sep 3, 2026 •

edited

Loading

`db5e6b1`

github-actions Bot commented Sep 3, 2026 •

edited

Loading

github-actions Bot commented Sep 3, 2026 •

edited

Loading