Uh oh!
There was an error while loading. Please reload this page.
[world-vercel] Use v3 stream endpoint (supports transparent reconnect on timeout) - #2424
Merged
Conversation
Point the world-vercel live-stream reader at the v3 stream endpoint. On a max-duration timeout (or mid-stream connection drop) the v3 server errors the response body rather than closing it cleanly, which is what lets the reconnecting reader resume from the next chunk instead of treating the timeout as end-of-stream. Writes, completion, and snapshot reads stay on v2. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 2fb4892 The changes in this PR will be included in the next version bump. This PR includes changesets to release 17 packages
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 |
Contributor
Contributor
📊 Benchmark Results
workflow with no steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express workflow with 1 step💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express | Nitro workflow with 10 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express | Nitro workflow with 25 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) workflow with 50 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Nitro | Express Promise.all with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Promise.all with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro Promise.all with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Promise.race with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express Promise.race with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express | Nitro Promise.race with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express | Nitro workflow with 10 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) workflow with 25 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) workflow with 50 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro workflow with 10 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Next.js (Turbopack) | Express workflow with 25 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) workflow with 50 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Stream Benchmarks(includes TTFB metrics)workflow with stream💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Nitro | Express stream pipeline with 5 transform steps (1MB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro 10 parallel streams (1MB each)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Nitro | Next.js (Turbopack) fan-out fan-in 10 streams (1MB each)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
|
Contributor
🧪 E2E Test Results✅ All tests passed Summary
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
✅ 📋 Other
|
VaguelySerious
marked this pull request as ready for review
June 15, 2026 13:05
Uh oh!
There was an error while loading. Please reload this page.
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
karthikscale3
approved these changes
Jun 22, 2026
karthikscale3
left a comment
Contributor
There was a problem hiding this comment.
Reviewed for blockers and regressions. I did not find any issues.
| // (chunks/info/list) stay on v2. | ||
| function getStreamReadUrl(name: string, runId: string, httpConfig: HttpConfig) { | ||
| return new URL( | ||
| `${httpConfig.baseUrl}/v3/runs/${encodeURIComponent(runId)}/stream/${encodeURIComponent(name)}` |
Contributor
There was a problem hiding this comment.
AI Review: Verified that only live stream reads move to the v3 endpoint while writes, close, and snapshot reads stay on v2, preserving existing write semantics while enabling reconnect-on-timeout behavior.
Contributor
Backport to To resolve manually, push a backport branch and open a PR against git fetch origin stable
git checkout -b backport/pr-2424-to-stable origin/stable
git cherry-pick -S d476d7aaf6fd58d5d7241d2152fb7a705a27c4e4 # -S signs the commit# Fix conflicts, then:
git add -A
git cherry-pick --continue
git push -u origin backport/pr-2424-to-stable
gh pr create --base stable --head backport/pr-2424-to-stable \
--title "Backport #2424: <original PR title>" \
--body "Manual backport of #2424 (cherry-pick d476d7aaf6fd) to \`stable\`." |
This was referenced Jun 23, 2026
pranaygp added a commit
that referenced
this pull request
Jun 23, 2026
…testing * origin/main: Trace /flow route initialization (#2592) Version Packages (beta) (#2591) feat(web): add trace step shortcut helper (#2582) [web-shared] reskin json viewer (no duplicates, better colours and navigation) (#2434) Send occurredAt with workflow events (#2580) docs: use actual eve logo and tidy OSS nav dropdown (#2586) Display occurredAt in trace details (#2581) fix(next): discover root entrypoints (#2564) [core] Turbo: skip the unused run_started event-log preload (#2569) fix(next): prewarm SWC plugin cache (#2538) [world-vercel] Use v3 stream endpoint (supports transparent reconnect on timeout) (#2424) [core] Retry stream reopen against the reconnect budget (#2334) Add Platformatic World to worlds-manifest.json (#1450) docs: derive section landing-page cards from the page tree + lint drift (#2567)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Needs V3 stream API to be live on the server first.
Point the
world-vercellive-stream reader (world.streams.get, used byrun.getReadable()) at the v3 stream endpoint instead of v2. Writes, stream completion, and snapshot reads (chunks/info/list) stay on v2 — only the long-lived live read is affected.Why
On the v3 endpoint the server errors the response body on a max-duration timeout (or a mid-stream connection drop) rather than closing it cleanly. That thrown error is exactly what the reconnecting reader (
createReconnectingFramedStream) needs to resume from the next chunk viastartIndex. On v2 the server closes cleanly, which the reader treats as end-of-stream — so today long-lived streams silently truncate at the server's 2-minute limit. This change makes object-stream reads (e.g. the AI chatUIMessageChunkstream) transparently survive the timeout.The reconnecting reader already shipped (#2318 on
main, #1847 onstable); it's been inert because the server never errored on timeout. This flips it on.