[world-postgres] Drive LISTEN reconnect retries in the invoke test the way consumers do by pranaygp · Pull Request #4809 · vercel/workflow

pranaygp · 2026-10-09T20:03:33Z

Summary

reconnects a terminated real LISTEN client and receives later notifications in packages/world-postgres/test/invoke.test.ts can time out with Error: Timed out waiting for integration state at its listenerPid poll (seen while verifying vercel/workflow#4785: 1 in 13 local full-suite runs, failing after 16,046 ms). The test made exactly one reconnect attempt, and nothing retried it when it failed. Production behaves correctly; this is test-only.

Follow-up to vercel/workflow#4785, which fixed the suite's other flake (FATAL 57P01 at container teardown). The two are independent.

Why it flaked

createInvocationNotifications reconnects lazily: only watch() and wait() call ensureListening(), and only once the 1s backoff after a disconnect has passed. Each attempt has 1s connect and LISTEN timeouts. Both consumers in invocations.ts read, then wait(revision, INVOCATION_FALLBACK_MS), in a loop, so a failed attempt is retried on their next wait.

The test instead called wait() twice (once inside the backoff, once just past it, which makes the single attempt) and then polled pg_stat_activity for 15s without calling wait() again. One slow attempt on a loaded runner stranded it: disconnected() set a new backoff and nothing triggered another attempt.

A probe ran the old sequence with the listener's first reconnect rejected the way pg rejects a connect timeout:

shape	failed attempts	result
old test	0	ok, 1,086 ms, 1 attempt
old test	1	timed out after 16,048 ms, 1 attempt (the observed failure)
old test	2	timed out after 16,045 ms, 1 attempt
consumer-style loop	0	ok, 1,078 ms, 1 attempt
consumer-style loop	1	ok, 2,125 ms, 2 attempts
consumer-style loop	2	ok, 3,182 ms, 3 attempts

Fix

Poll the way consumers do: read, then watch.wait(watch.revision, INVOCATION_FALLBACK_MS) while not ready. The initial subscription uses the same loop: a failed first connect also satisfied the old revision > 0 check and then stranded the firstPid poll the same way.
Make the listener's first reconnect fail on purpose (a Client.prototype.connect spy scoped to this listener's application_name), so the test always covers a retried attempt instead of only when CI is slow. It asserts at least 3 listener connects: the initial one, the injected failure, and the retry.
Tighten readiness: pg_stat_activity reports a backend as idle right after connect, before its LISTEN runs, so the pid filter now also requires query LIKE 'LISTEN %'. The test waits for the listener's "Invocation notifications restored" transition, which is logged right before it wakes its watches, before taking the notification baseline. So the final notification check can't be satisfied by the reconnect's own wake.

The test is renamed to say it covers a retried attempt.

Verification

Mutation check: with poll()'s wait() swapped for a plain 1s sleep (no retry driven), the new test fails exactly like the flake: Timed out waiting for integration state after 16,364 ms. With the fix it passes in about 2.2 s.
Suite: cd packages/world-postgres && for i in $(seq 1 10); do FORCE_COLOR=0 pnpm test; done against local Docker: 10/10 green, 321/321 tests each, no unhandled errors.

🤖 Generated with Claude Code

…e way consumers do The "reconnects a terminated real LISTEN client" test made exactly one reconnect attempt: invocation notifications reconnect only from watch() and wait() once the 1s backoff has passed, and the test called wait() twice and then polled pg_stat_activity for 15s. If that one attempt failed (1s connect and LISTEN timeouts, so a loaded runner is enough), nothing retried it and the poll timed out. Production consumers in invocations.ts read and then wait(revision, INVOCATION_FALLBACK_MS) in a loop, so they retry on the next wait; the reconnect behaviour itself is correct. Poll the way consumers do, waiting between reads, and make the listener's first reconnect fail on purpose so the test always covers a retried attempt. The initial subscription gets the same loop: a failed first connect also satisfied the old revision > 0 check and stranded the pid poll. Readiness now means the backend has run LISTEN (pg_stat_activity reports a backend as idle before its LISTEN runs), and the restored transition is awaited before taking the notification baseline, so the final notification check cannot be satisfied by the reconnect's own wake. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

changeset-bot · 2026-10-09T20:03:38Z

🦋 Changeset detected

Latest commit: 7185af5

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

This PR includes changesets to release 0 packages

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

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

Copilot

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

vercel · 2026-10-09T20:03:46Z

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

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

github-actions · 2026-10-09T20:03:53Z

🧪 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.

experimental_retention: 0 purges the run payloads once the run finishes (express · vercel-prod / vercel / node / production)
resumes in flight during the takeover are never lost: each lands in exactly one log (fastify · vercel-prod / vercel / quickjs / production)

🛠 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.

run-pickup-stall · runs app-generated source against a registered step (tanstack-start) · at 20:15:03Z · abandoned wrun_01M4RW1T79RH8SQ77Y57QNT7T9
cold-start-warmup · suite warmup (tanstack-start) · at 20:15:05Z · abandoned wrun_01M4RW1T7D2QTPY8ZX73J8WB0S
run-pickup-stall · hookCleanupTestWorkflow - hook token reuse after workflow completion (nextjs-webpack) · at 20:23:15Z · abandoned wrun_01M4RWGTAFE9KHQX15WTY8CPH8

E2E Test Summary

Summary

	Passed	Skipped	Total
✅ ▲ Vercel Production	3982	878	4860
✅ 💻 Local Development	4669	551	5220
✅ 📦 Local Production	4669	551	5220
✅ 🐘 Local Postgres	4669	551	5220
✅ 🪟 Windows	348	12	360
✅ 🌐 Cross-language Conformance	68	87	155
✅ dynamic-runs	0	0	0
✅ vercel-http-transport	897	183	1080
✅ vercel-multi-region	27	0	27
✅ vercel-ws-transport	607	113	720
Total	19936	2926	22862

Details by Category

✅ ▲ Vercel Production

App	Passed	Skipped
✅ astro-node	145	35
✅ astro-quickjs	145	35
✅ example-node	145	35
✅ example-quickjs	145	35
✅ express-node	145	35
✅ express-quickjs	145	35
✅ fastify-node	145	35
✅ fastify-quickjs	145	35
✅ hono-node	145	35
✅ hono-quickjs	145	35
✅ nest-node	145	35
✅ nest-quickjs	145	35
✅ nextjs-turbopack-node	172	8
✅ nextjs-turbopack-quickjs	172	8
✅ nextjs-webpack-node	172	8
✅ nextjs-webpack-quickjs	172	8
✅ nitro-node	145	35
✅ nitro-quickjs	145	35
✅ nuxt-node	145	35
✅ nuxt-quickjs	145	35
✅ python-node	66	114
✅ sveltekit-node	164	16
✅ sveltekit-quickjs	164	16
✅ tanstack-start-node	145	35
✅ tanstack-start-quickjs	145	35
✅ vite-node	145	35
✅ vite-quickjs	145	35

✅ 💻 Local Development

App	Passed	Skipped
✅ astro-stable-node	151	29
✅ astro-stable-quickjs	151	29
✅ express-stable-node	151	29
✅ express-stable-quickjs	151	29
✅ fastify-stable-node	151	29
✅ fastify-stable-quickjs	151	29
✅ hono-stable-node	151	29
✅ hono-stable-quickjs	151	29
✅ nest-stable-node	151	29
✅ nest-stable-quickjs	151	29
✅ nextjs-turbopack-canary-node	179	1
✅ nextjs-turbopack-canary-quickjs	179	1
✅ nextjs-turbopack-quickjs-snapshot	179	1
✅ nextjs-turbopack-stable-node	179	1
✅ nextjs-turbopack-stable-quickjs	179	1
✅ nextjs-webpack-canary-node	179	1
✅ nextjs-webpack-canary-quickjs	179	1
✅ nextjs-webpack-stable-node	179	1
✅ nextjs-webpack-stable-quickjs	179	1
✅ nitro-stable-node	151	29
✅ nitro-stable-quickjs	151	29
✅ nuxt-stable-node	151	29
✅ nuxt-stable-quickjs	151	29
✅ sveltekit-stable-node	170	10
✅ sveltekit-stable-quickjs	170	10
✅ tanstack-start-node	151	29
✅ tanstack-start-quickjs	151	29
✅ vite-stable-node	151	29
✅ vite-stable-quickjs	151	29

✅ 📦 Local Production

App	Passed	Skipped
✅ astro-stable-node	151	29
✅ astro-stable-quickjs	151	29
✅ express-stable-node	151	29
✅ express-stable-quickjs	151	29
✅ fastify-stable-node	151	29
✅ fastify-stable-quickjs	151	29
✅ hono-stable-node	151	29
✅ hono-stable-quickjs	151	29
✅ nest-stable-node	151	29
✅ nest-stable-quickjs	151	29
✅ nextjs-turbopack-canary-node	179	1
✅ nextjs-turbopack-canary-quickjs	179	1
✅ nextjs-turbopack-quickjs-snapshot	179	1
✅ nextjs-turbopack-stable-node	179	1
✅ nextjs-turbopack-stable-quickjs	179	1
✅ nextjs-webpack-canary-node	179	1
✅ nextjs-webpack-canary-quickjs	179	1
✅ nextjs-webpack-stable-node	179	1
✅ nextjs-webpack-stable-quickjs	179	1
✅ nitro-stable-node	151	29
✅ nitro-stable-quickjs	151	29
✅ nuxt-stable-node	151	29
✅ nuxt-stable-quickjs	151	29
✅ sveltekit-stable-node	170	10
✅ sveltekit-stable-quickjs	170	10
✅ tanstack-start-node	151	29
✅ tanstack-start-quickjs	151	29
✅ vite-stable-node	151	29
✅ vite-stable-quickjs	151	29

✅ 🐘 Local Postgres

App	Passed	Skipped
✅ astro-stable-node	151	29
✅ astro-stable-quickjs	151	29
✅ express-stable-node	151	29
✅ express-stable-quickjs	151	29
✅ fastify-stable-node	151	29
✅ fastify-stable-quickjs	151	29
✅ hono-stable-node	151	29
✅ hono-stable-quickjs	151	29
✅ nest-stable-node	151	29
✅ nest-stable-quickjs	151	29
✅ nextjs-turbopack-canary-node	179	1
✅ nextjs-turbopack-canary-quickjs	179	1
✅ nextjs-turbopack-quickjs-snapshot	179	1
✅ nextjs-turbopack-stable-node	179	1
✅ nextjs-turbopack-stable-quickjs	179	1
✅ nextjs-webpack-canary-node	179	1
✅ nextjs-webpack-canary-quickjs	179	1
✅ nextjs-webpack-stable-node	179	1
✅ nextjs-webpack-stable-quickjs	179	1
✅ nitro-stable-node	151	29
✅ nitro-stable-quickjs	151	29
✅ nuxt-stable-node	151	29
✅ nuxt-stable-quickjs	151	29
✅ sveltekit-stable-node	170	10
✅ sveltekit-stable-quickjs	170	10
✅ tanstack-start-node	151	29
✅ tanstack-start-quickjs	151	29
✅ vite-stable-node	151	29
✅ vite-stable-quickjs	151	29

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack-node	174	0	6
✅ nextjs-turbopack-quickjs	174	0	6

✅ 🌐 Cross-language Conformance

App	Passed	Failed	Skipped
✅ python	68	0	87

✅ dynamic-runs

App	Passed	Failed	Skipped
✅ astro-vercel	0	0	0
✅ example-vercel	0	0	0
✅ express-vercel	0	0	0
✅ fastify-vercel	0	0	0
✅ hono-vercel	0	0	0
✅ nest-vercel	0	0	0
✅ nextjs-turbopack-vercel	0	0	0
✅ nextjs-webpack-vercel	0	0	0
✅ nitro-vercel	0	0	0
✅ nuxt-vercel	0	0	0
✅ sveltekit-vercel	0	0	0
✅ tanstack-start-vercel	0	0	0
✅ vite-vercel	0	0	0

✅ vercel-http-transport

App	Passed	Skipped
✅ example	145	35
✅ express	145	35
✅ hono	145	35
✅ nextjs-turbopack	172	8
✅ nitro	145	35
✅ vite	145	35

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

✅ vercel-ws-transport

App	Passed	Skipped
✅ example	145	35
✅ express	145	35
✅ nextjs-turbopack	172	8
✅ vite	145	35

📋 View full workflow run

github-actions · 2026-10-09T20:03:56Z

📊 Workflow Benchmarks

commit 7185af5 · Mon, 12 Oct 2026 20:27:35 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	1864 (+41%) 🔻	2297 🔴 (+34%) 🔻	2339 🔴 (+31%) 🔻	2376 🔴 (+29%) 🔻	30
TTFS	stream	1896 (+580%) 🔻	1984 🔴 (+34%) 🔻	2025 🔴 (+23%) 🔻	2650 🔴 (+36%) 🔻	30
TTFS	hook + stream	1888 (+334%) 🔻	2338 🔴 (+31%) 🔻	2442 🔴 (+28%) 🔻	5408 🔴 (+171%) 🔻	30
Fan-out TTFS	Promise.all(100 steps)	547 (+19%) 🔻	814 (-57%) 💚	2407 (+25%) 🔻	2476 (+29%) 🔻	10
Fan-out TTLS	Promise.all(100 steps)	2490 (+90%) 🔻	4674 (+12%)	6218 (+22%) 🔻	8467 (+57%) 🔻	10
STSO	1020 steps (inline)	76 (-9.5%)	103 (-10%)	117 (-14%)	189 (-13%)	1019
WO	1020 steps	104324 (-7.3%)	104324 (-7.3%)	104324 (-7.3%)	104324 (-7.3%)	1

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

1020 steps (inline)

Cumulative STSO time: main 112265ms → this run 104091ms (Δ -8174ms, -7%)

 50-100 ms  ███████████████░░░░░░░░┃  main 417  this 658  +241
100-150 ms  ███████████┃████████      main 542  this 336  -206
150-200 ms  ┃█                        main  46  this  16   -30
200-250 ms  ┃                         main   8  this   4    -4
250-300 ms  ┃                         main   4  this   3    -1
300-350 ms  ┃                         main   0  this   1    +1
350-400 ms  ┃                         main   1  this   0    -1
400-450 ms  ┃                         main   1  this   1    +0

📜 Previous results (1)

`ccaff71`

Fri, 09 Oct 2026 20:18:06 GMT · run logs

vercel / nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	1888 (+486%) 🔻	2024 🔴 (+34%) 🔻	2079 🔴 (+32%) 🔻	2103 🔴 (+23%) 🔻	30
TTFS	stream	1599 (+348%) 🔻	1965 🔴 (+33%) 🔻	1988 🔴 (+32%) 🔻	2081 🔴 (+22%) 🔻	30
TTFS	hook + stream	2210 (+231%) 🔻	2340 🔴 (+39%) 🔻	2360 🔴 (+37%) 🔻	2499 🔴 (+32%) 🔻	30
Fan-out TTFS	Promise.all(100 steps)	621 (+11%)	766 (-19%) 💚	795 (-24%) 💚	2725 (+56%) 🔻	10
Fan-out TTLS	Promise.all(100 steps)	2614 (+12%)	4441 (+3.1%)	4546 (+0.8%)	10861 (+72%) 🔻	10
STSO	1020 steps (inline)	114 (+36%) 🔻	139 (-0.7%)	157 (-11%)	207 (-47%) 💚	1019
WO	1020 steps	138543 (-1.3%)	138543 (-1.3%)	138543 (-1.3%)	138543 (-1.3%)	1

ℹ️ Metric definitions & methodology

_{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.}

_{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)}

_{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}

_{🔴 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. Streaming delivery performance is measured in durabench.}

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

github-actions · 2026-10-09T20:04:28Z

Sim World

Simulated world deterministic testing for races. Traces

🟢 world-sim scenario book — 0 fail of 42 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
✅ `step-vs-timer-early-settlement`	completed	8	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-10-09T20:05:30Z

Framework	Flow route	Step reg.	Framework output
hono	267.4 KiB (±0)	95.5 KiB (±0)	1.99 MiB (±0)
nextjs-turbopack	274.8 KiB (±0)	426 B (±0)	970.8 KiB (±0)

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.

7185af5 · run

…sten-reconnect-flake Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>

…nect test's baselines pg_stat_activity lists the LISTEN before the listener has read its reply. If the first connect failed (degraded), its "restored" log and wake can land after beforeRestore/beforeDisconnect are sampled, satisfying both waits before the terminated backend reconnects; secondPid is then undefined. A notification follows the LISTEN reply on the same socket, so round-trip one before sampling. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>

…sten-reconnect-flake Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>

pranaygp requested a review from a team as a code owner October 9, 2026 20:03

Copilot AI balanced review requested due to automatic review settings October 9, 2026 20:03

Copilot AI reviewed Oct 9, 2026

vercel Bot deployed to Preview – workflow-docs October 9, 2026 20:05

View deployment

pranaygp mentioned this pull request Oct 9, 2026

[world-postgres] Keep a dropped connection in the World's own pool from ending the process #4812

Merged

vercel Bot and others added 2 commits October 12, 2026 20:00

Merge remote-tracking branch 'origin/main' into pgp/world-postgres-li…

b4b9027

…sten-reconnect-flake Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>

vercel Bot deployed to Preview – workflow-docs October 12, 2026 20:03

View deployment

Merge remote-tracking branch 'origin/main' into pgp/world-postgres-li…

7185af5

…sten-reconnect-flake Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>

vercel Bot deployed to Preview – workflow-docs October 12, 2026 20:13

View deployment

Navigation Menu

Repository navigation

[world-postgres] Drive LISTEN reconnect retries in the invoke test the way consumers do - #4809

[world-postgres] Drive LISTEN reconnect retries in the invoke test the way consumers do#4809
pranaygp wants to merge 4 commits into
mainfrom
pgp/world-postgres-listen-reconnect-flake

pranaygp commented Oct 9, 2026

Uh oh!

changeset-bot Bot commented Oct 9, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

vercel Bot commented Oct 9, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 9, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 9, 2026 •

edited

Loading

`ccaff71`

Uh oh!

github-actions Bot commented Oct 9, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 9, 2026 •

edited

Loading

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

pranaygp commented Oct 9, 2026

Summary

Why it flaked

Fix

Verification

Uh oh!

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

Uh oh!

🦋 Changeset detected

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

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

Uh oh!

Uh oh!

github-actions Bot commented Oct 9, 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 Oct 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📊 Workflow Benchmarks

ccaff71

Uh oh!

github-actions Bot commented Oct 9, 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 Oct 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

changeset-bot Bot commented Oct 9, 2026 •

edited

Loading

vercel Bot commented Oct 9, 2026 •

edited

Loading

github-actions Bot commented Oct 9, 2026 •

edited

Loading

github-actions Bot commented Oct 9, 2026 •

edited

Loading

`ccaff71`

github-actions Bot commented Oct 9, 2026 •

edited

Loading

github-actions Bot commented Oct 9, 2026 •

edited

Loading