[world-postgres] Deliver queue messages without implicit HTTP deadlines by VaguelySerious · Pull Request #4137 · vercel/workflow

VaguelySerious · 2026-09-11T23:56:56Z

Fixes #3811, closes #4114.

Carries #4114 (@komly) into a signed PR with review findings addressed. The original author is credited via Co-authored-by.

What

executeMessageOverHttp used the global fetch, so every queue delivery inherited undici's default 300s headersTimeout / bodyTimeout. A delivery executes the workflow body inline and the handler responds only once that work is done, so any inline step slower than about five minutes was declared crashed (TypeError: fetch failed), the Graphile task failed, and the message was redelivered while the original delivery was still running: two concurrent executions of the same steps, as reported in #3811.

Deliveries now go over @workflow/world/node-http.js (the node:http client world-local and world-vercel already use behind WORKFLOW_NODE_HTTP), with no deadline by default. Graphile's abort signal still cancels the in-flight request on close().

Changes relative to #4114:

The deadlines are operator-configurable via WORKFLOW_POSTGRES_HEADERS_TIMEOUT_MS / WORKFLOW_POSTGRES_BODY_TIMEOUT_MS (default 0, unbounded), mirroring world-local's WORKFLOW_LOCAL_*_TIMEOUT_MS. fix(world-postgres): remove implicit queue HTTP deadlines #4114 hard-coded 0, which leaves an operator no way to have a hung handler redelivered rather than hold its worker slot until restart. Documented in docs/content/worlds/v5/postgres.mdx.
Requests dispatch on a keep-alive pool the queue creates and destroys in close(), rather than Node's process-global http.globalAgent. (I verified the global agent's 5s socket timeout does not tear down a slow request, so this is hygiene, not a correctness fix.)
The Testcontainers integration test always uses a container, like the package's other integration tests; the WORKFLOW_POSTGRES_URL branch that threw on a non-loopback URL and the README additions are dropped.
undici is added as a devDependency only, so the integration test can pin the global dispatcher to a 10ms deadline and prove the delivery no longer goes through fetch without a five-minute wait.

Tests

test/queue-http.test.ts (Testcontainers, real Graphile Worker + loopback HTTP): a delivery whose headers or body arrive after the global fetch deadline completes on attempt 1 with no redelivery; shutdown still aborts a pending delivery and releases its job. The two healthy-delivery cases fail against main's queue.ts.
src/queue.test.ts: existing fetch-stub tests rewritten against loopback servers (from fix(world-postgres): remove implicit queue HTTP deadlines #4114), plus: defaults are unbounded and env parsing rejects garbage; an operator-set 50ms headers deadline fails a stalled delivery with ETIMEDOUT and schedules no replacement job.

Related observation (not changed here)

world-local bounds the same loopback delivery at 30s by default (WORKFLOW_LOCAL_HEADERS_TIMEOUT_MS, #3255) and redelivers on expiry. If its handler also executes inline steps before responding, an inline step over 30s would hit the same double-execution there. I have not verified that empirically; flagging it for a separate look.

🤖 Generated with Claude Code

…dlines `executeMessageOverHttp` used the global `fetch`, so a delivery inherited undici's default 300s headers/body deadlines. A delivery executes the workflow body inline and responds only when that work is done, so any inline step slower than five minutes was declared crashed and redelivered while the original was still running, executing the same steps twice. Deliveries now go over `@workflow/world/node-http.js` on a queue-owned keep-alive pool, with no deadline unless the operator sets `WORKFLOW_POSTGRES_HEADERS_TIMEOUT_MS` / `WORKFLOW_POSTGRES_BODY_TIMEOUT_MS`. Graphile's abort signal still cancels the request on shutdown. Co-authored-by: Dmitry Petrov <Komly@yandex.ru> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

changeset-bot · 2026-09-11T23:57:02Z

🦋 Changeset detected

Latest commit: 5183f78

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@workflow/world-postgres	Patch

Not sure what this means? Click here to learn what changesets are.

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

vercel · 2026-09-11T23:57:12Z

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

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

github-actions · 2026-09-11T23:57:15Z

🧪 E2E Test Results

✅ All tests passed

⚠️ 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.

sleepWinsRaceWorkflow (tanstack-start · local-dev / local / node)
sleepWinsRaceWorkflow (vite · local-dev / local / quickjs / stable)
stepWinsRaceWorkflow (tanstack-start · local-dev / local / node)

🛠 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 00:02:12Z · abandoned wrun_01M29EQ0FWW83R3XZ2NC5E4SHD
run-pickup-stall · hookCleanupTestWorkflow - hook token reuse after workflow completion (nextjs-webpack) · at 00:07:10Z · abandoned wrun_01M29F0HE26MGCWNYH3WZV9SXA

E2E Test Summary

Summary

	Passed	Skipped	Total
✅ ▲ Vercel Production	3662	685	4347
✅ 💻 Local Development	3998	510	4508
✅ 📦 Local Production	3998	510	4508
✅ 🐘 Local Postgres	3998	510	4508
✅ 🪟 Windows	320	2	322
✅ 🌐 Cross-language Conformance	68	74	142
✅ vercel-http-transport	823	143	966
✅ vercel-multi-region	27	0	27
✅ vercel-ws-transport	557	87	644
Total	17451	2521	19972

Details by Category

✅ ▲ Vercel Production

App	Passed	Skipped
✅ astro-node	133	28
✅ astro-quickjs	133	28
✅ example-node	133	28
✅ example-quickjs	133	28
✅ express-node	133	28
✅ express-quickjs	133	28
✅ fastify-node	133	28
✅ fastify-quickjs	133	28
✅ hono-node	133	28
✅ hono-quickjs	133	28
✅ nest-node	133	28
✅ nest-quickjs	133	28
✅ nextjs-turbopack-node	158	3
✅ nextjs-turbopack-quickjs	158	3
✅ nextjs-webpack-node	158	3
✅ nextjs-webpack-quickjs	158	3
✅ nitro-node	133	28
✅ nitro-quickjs	133	28
✅ nuxt-node	133	28
✅ nuxt-quickjs	133	28
✅ python-node	66	95
✅ sveltekit-node	152	9
✅ sveltekit-quickjs	152	9
✅ tanstack-start-node	133	28
✅ tanstack-start-quickjs	133	28
✅ vite-node	133	28
✅ vite-quickjs	133	28

✅ 💻 Local Development

App	Passed	Skipped
✅ astro-stable-node	134	27
✅ astro-stable-quickjs	134	27
✅ express-stable-node	134	27
✅ express-stable-quickjs	134	27
✅ fastify-stable-node	134	27
✅ fastify-stable-quickjs	134	27
✅ hono-stable-node	134	27
✅ hono-stable-quickjs	134	27
✅ nest-stable-node	134	27
✅ nest-stable-quickjs	134	27
✅ nextjs-turbopack-canary-node	160	1
✅ nextjs-turbopack-canary-quickjs	160	1
✅ nextjs-turbopack-stable-node	160	1
✅ nextjs-turbopack-stable-quickjs	160	1
✅ nextjs-webpack-canary-node	160	1
✅ nextjs-webpack-canary-quickjs	160	1
✅ nextjs-webpack-stable-node	160	1
✅ nextjs-webpack-stable-quickjs	160	1
✅ nitro-stable-node	134	27
✅ nitro-stable-quickjs	134	27
✅ nuxt-stable-node	134	27
✅ nuxt-stable-quickjs	134	27
✅ sveltekit-stable-node	153	8
✅ sveltekit-stable-quickjs	153	8
✅ tanstack-start-node	134	27
✅ tanstack-start-quickjs	134	27
✅ vite-stable-node	134	27
✅ vite-stable-quickjs	134	27

✅ 📦 Local Production

App	Passed	Skipped
✅ astro-stable-node	134	27
✅ astro-stable-quickjs	134	27
✅ express-stable-node	134	27
✅ express-stable-quickjs	134	27
✅ fastify-stable-node	134	27
✅ fastify-stable-quickjs	134	27
✅ hono-stable-node	134	27
✅ hono-stable-quickjs	134	27
✅ nest-stable-node	134	27
✅ nest-stable-quickjs	134	27
✅ nextjs-turbopack-canary-node	160	1
✅ nextjs-turbopack-canary-quickjs	160	1
✅ nextjs-turbopack-stable-node	160	1
✅ nextjs-turbopack-stable-quickjs	160	1
✅ nextjs-webpack-canary-node	160	1
✅ nextjs-webpack-canary-quickjs	160	1
✅ nextjs-webpack-stable-node	160	1
✅ nextjs-webpack-stable-quickjs	160	1
✅ nitro-stable-node	134	27
✅ nitro-stable-quickjs	134	27
✅ nuxt-stable-node	134	27
✅ nuxt-stable-quickjs	134	27
✅ sveltekit-stable-node	153	8
✅ sveltekit-stable-quickjs	153	8
✅ tanstack-start-node	134	27
✅ tanstack-start-quickjs	134	27
✅ vite-stable-node	134	27
✅ vite-stable-quickjs	134	27

✅ 🐘 Local Postgres

App	Passed	Skipped
✅ astro-stable-node	134	27
✅ astro-stable-quickjs	134	27
✅ express-stable-node	134	27
✅ express-stable-quickjs	134	27
✅ fastify-stable-node	134	27
✅ fastify-stable-quickjs	134	27
✅ hono-stable-node	134	27
✅ hono-stable-quickjs	134	27
✅ nest-stable-node	134	27
✅ nest-stable-quickjs	134	27
✅ nextjs-turbopack-canary-node	160	1
✅ nextjs-turbopack-canary-quickjs	160	1
✅ nextjs-turbopack-stable-node	160	1
✅ nextjs-turbopack-stable-quickjs	160	1
✅ nextjs-webpack-canary-node	160	1
✅ nextjs-webpack-canary-quickjs	160	1
✅ nextjs-webpack-stable-node	160	1
✅ nextjs-webpack-stable-quickjs	160	1
✅ nitro-stable-node	134	27
✅ nitro-stable-quickjs	134	27
✅ nuxt-stable-node	134	27
✅ nuxt-stable-quickjs	134	27
✅ sveltekit-stable-node	153	8
✅ sveltekit-stable-quickjs	153	8
✅ tanstack-start-node	134	27
✅ tanstack-start-quickjs	134	27
✅ vite-stable-node	134	27
✅ vite-stable-quickjs	134	27

✅ 🪟 Windows

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

✅ 🌐 Cross-language Conformance

App	Passed	Failed	Skipped
✅ python	68	0	74

✅ vercel-http-transport

App	Passed	Skipped
✅ example	133	28
✅ express	133	28
✅ hono	133	28
✅ nextjs-turbopack	158	3
✅ nitro	133	28
✅ vite	133	28

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

✅ vercel-ws-transport

App	Passed	Skipped
✅ example	133	28
✅ express	133	28
✅ nextjs-turbopack	158	3
✅ vite	133	28

📋 View full workflow run

github-actions · 2026-09-11T23:57:19Z

📊 Workflow Benchmarks

commit 5183f78 · Sat, 12 Sep 2026 00:14:27 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	315 (-75%) 💚	1633 🔴 (+16%) 🔻	1659 🔴 (+15%)	1965 🔴 (+19%) 🔻	30
TTFS	stream	161 (-26%) 💚	1621 🔴 (+19%) 🔻	1646 🔴 (+19%) 🔻	1684 🔴 (+16%) 🔻	30
TTFS	hook + stream	1809 (+12%)	2028 🔴 (+17%) 🔻	2168 🔴 (+23%) 🔻	6932 🔴 (+251%) 🔻	30
Fan-out TTFS	Promise.all(100 steps)	472 (±0%)	671 (-2.9%)	822 (-4.9%)	1925 (+8.6%)	10
Fan-out TTLS	Promise.all(100 steps)	1979 (+3.2%)	5425 (+105%) 🔻	5558 (+24%) 🔻	9002 (+16%) 🔻	10
STSO	1020 steps (inline)	123 (-4.7%)	139 (-16%) 💚	156 (-17%) 💚	200 (-44%) 💚	1019
WO	1020 steps	141379 (-14%)	141379 (-14%)	141379 (-14%)	141379 (-14%)	1
CRTT	first chunk (pooled)	60 (-1.6%)	91 (-38%) 💚	106 (-52%) 💚	165 (-57%) 💚	28

Streams

Scenario	CRTT 1st	p75	p90	p99	CDV max	iters
paced control (100/s, 60B)	86 (-19%)	151 (-50%)	284 (-22%)	697 (+14%)	174 (-19%)	10
size sweep (100/s, 160B-12KB)	79 (-35%)	139 (-73%)	208 (-73%)	592 (-41%)	178 (-53%)	10
replay gateway-gpt-5.4-nano-2000t (1x)	86 (-30%)	121 (-58%)	152 (-71%)	324 (-68%)	150 (-58%)	3
replay eve-gpt-5.6-sol-2000t (1x)	70.5 (-50%)	120 (-46%)	145 (-49%)	238 (-54%)	177 (-46%)	2
replay eve-gpt-5.6-sol-2000t (2x)	86 (-37%)	150 (-67%)	221 (-72%)	377 (-67%)	222 (-65%)	3

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

1020 steps (inline)

Cumulative STSO time: main 164862ms → this run 141139ms (Δ -23723ms, -14%)

100-150 ms  █████████████░░░░░░░░░░┃  main 483  this 882  +399
150-200 ms  ██┃██████████             main 465  this 126  -339
200-250 ms  ┃                         main  34  this   9   -25
250-300 ms  ┃                         main  15  this   0   -15
300-350 ms  ┃                         main  11  this   0   -11
350-400 ms  ┃                         main   6  this   2    -4
400-450 ms  ┃                         main   2  this   0    -2
450-500 ms  ┃                         main   1  this   0    -1
500-550 ms  ┃                         main   1  this   0    -1
600-650 ms  ┃                         main   1  this   0    -1

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

variant  RTT 1ms→5s+             avg         p50         p90         p99     n
control  ······▄█▂▁···  134.9 (-34%)  113 (-37%)  284 (-22%)  697 (+14%)  3000
sweep    ······▅█▁▁···  124.2 (-58%)  109 (-53%)  208 (-73%)  592 (-41%)  3000
gw 1x    ·····▁▇█▁····  107.3 (-48%)  104 (-37%)  152 (-71%)  324 (-68%)  5295
eve 1x   ·····▁██▁····  102.4 (-46%)   95 (-43%)  145 (-49%)  238 (-54%)  5186
eve 2x   ·····▁▄█▂····  130.7 (-61%)  117 (-54%)  221 (-72%)  377 (-67%)  7779

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

control  ▁▃▇▆▃█▅▁▁▂  115–165ms
sweep    ▅▂▄▅█▁▂▁▄█  110–144ms
gw 1x    █▁▂▃▅▄▁▁▇▁  100–123ms
eve 1x   ▃▂▅▃▁▁▇█▅▁  94–116ms
eve 2x   ▃▃▃▁▁▄▆█▅▂  105–173ms

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

sweep  ▄▅█▄▃▅▁  124–125ms

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

control  ▂▆▄▆▃█▂▃▁▅  31–48ms
sweep    ▁▁▇▆█▃▂▂▆▂  46–63ms
gw 1x    █▂▁▁▆▃▂▂▃▂  30–41ms
eve 1x   ▁▅▄▃▄▃██▇▇  19–24ms
eve 2x   ▅▅▁▂▂▄█▃▃▄  19–29ms

ℹ️ 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-12T00:00: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-12T00:00:48Z

Framework	Flow route	Step reg.	Framework output
hono	250.7 KiB (±0)	93.0 KiB (±0)	1.88 MiB (-1.2 KiB)
nextjs-turbopack	257.2 KiB (±0)	426 B (±0)	897.3 KiB (-380 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.

5183f78 · run

VaguelySerious · 2026-09-12T00:18:14Z

Closing: this work was moved onto the original PR #4114 as a follow-up commit, with the review notes posted there.

VaguelySerious requested a review from a team as a code owner September 11, 2026 23:56

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

VaguelySerious closed this Sep 12, 2026

VaguelySerious deleted the peter/postgres-queue-http-deadlines branch September 12, 2026 00:18

Navigation Menu

Uh oh!

[world-postgres] Deliver queue messages without implicit HTTP deadlines - #4137

[world-postgres] Deliver queue messages without implicit HTTP deadlines#4137
VaguelySerious wants to merge 1 commit into
mainfrom
peter/postgres-queue-http-deadlines

VaguelySerious commented Sep 11, 2026

Uh oh!

changeset-bot Bot commented Sep 11, 2026

Uh oh!

vercel Bot commented Sep 11, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 11, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 11, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 12, 2026

Uh oh!

github-actions Bot commented Sep 12, 2026

Uh oh!

VaguelySerious commented Sep 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

VaguelySerious commented Sep 11, 2026

What

Tests

Related observation (not changed here)

Uh oh!

changeset-bot Bot commented Sep 11, 2026

🦋 Changeset detected

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

🧪 E2E Test Results

⚠️ Flaky E2E Tests (passed on retry)

🛠 Infra Events (absorbed by the harness)

E2E Test Summary

Uh oh!

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

Uh oh!

📊 Workflow Benchmarks

Uh oh!

github-actions Bot commented Sep 12, 2026

Sim World

Uh oh!

github-actions Bot commented Sep 12, 2026

Uh oh!

VaguelySerious commented Sep 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

vercel Bot commented Sep 11, 2026 •

edited

Loading

github-actions Bot commented Sep 11, 2026 •

edited

Loading

github-actions Bot commented Sep 11, 2026 •

edited

Loading