Skip to content

Add format prefix to stream chunks and use .bin extension for chunk files (in world-local)#1020

Merged
TooTallNate merged 4 commits into
mainfrom
nate/stream-chunk-format-prefix
Feb 12, 2026
Merged

Add format prefix to stream chunks and use .bin extension for chunk files (in world-local)#1020
TooTallNate merged 4 commits into
mainfrom
nate/stream-chunk-format-prefix

Conversation

@TooTallNate
Copy link
Copy Markdown
Member

@TooTallNate TooTallNate commented Feb 12, 2026

Summary

Stream chunks were serialized as raw devalue text without the devl format prefix or any framing, unlike step inputs/outputs. This meant stream data couldn't go through the same hydration/deserialization pipeline used for other serialized data, and future encryption support (encr prefix) couldn't be applied to stream chunks.

Changes

@workflow/core (serialization.ts)

  • getSerializeStream: Each chunk is now individually wrapped with encodeWithFormatPrefix('devl', payload) inside a length-prefixed frame:
    [4-byte big-endian length][devl<devalue payload>]
    
  • getDeserializeStream: Buffers incoming data and extracts complete frames. Auto-detects framed vs legacy format:
    • If first 4 bytes form a plausible length → length-prefixed framed mode
    • Otherwise → legacy newline-delimited text parsing
  • Unit tests: 6 new tests covering framing, round-trip, concatenation (transport coalescing), splitting (arbitrary boundaries), and legacy fallback

@workflow/world-local (streamer.ts, fs.ts)

  • Stream chunk files now use .bin extension instead of .json (the content is binary, not JSON)
  • readFromStream lists both .bin and .json files for backwards compatibility with existing stored streams
  • Added listFilesByExtension() utility to fs.ts
  • Updated streamer.test.ts to expect .bin extension

Backwards Compatibility

  • getDeserializeStream falls back to legacy newline-delimited text parsing when the data is not length-prefixed
  • readFromStream reads both .bin (current) and .json (legacy) chunk files
  • New streams written after this change will have format prefix + length framing
  • All 313 core tests and 207 world-local tests pass

…k files

Stream chunks were serialized as raw devalue text without the 'devl'
format prefix, unlike step inputs/outputs. This meant stream data
couldn't go through the same hydration/deserialization pipeline.

Core changes (serialization.ts):
- getSerializeStream: each chunk is now individually wrapped with
  encodeWithFormatPrefix('devl', payload) — same as step data
- getDeserializeStream: handles both format-prefixed chunks (current)
  and legacy newline-delimited text (backwards compatible)

World-local changes (streamer.ts):
- Stream chunk files now use .bin extension instead of .json, since
  the content is binary (1-byte eof flag + serialized chunk data)
- Add listFilesByExtension() utility to fs.ts for generic file listing
Copilot AI review requested due to automatic review settings February 12, 2026 09:52
@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Feb 12, 2026

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Feb 12, 2026

🦋 Changeset detected

Latest commit: aaaf076

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

This PR includes changesets to release 16 packages
Name Type
@workflow/world-local Patch
@workflow/core Patch
@workflow/cli Patch
@workflow/world-postgres Patch
@workflow/builders Patch
@workflow/next Patch
@workflow/nitro Patch
@workflow/web-shared Patch
workflow Patch
@workflow/world-testing Patch
@workflow/astro Patch
@workflow/nest Patch
@workflow/rollup Patch
@workflow/sveltekit Patch
@workflow/vite Patch
@workflow/nuxt 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

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 12, 2026

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 0.032s (+1.6%) 1.005s (~) 0.973s 10 1.00x
💻 Local Express 0.032s (+5.2% 🔺) 1.005s (~) 0.973s 10 1.01x
💻 Local Next.js (Turbopack) 0.034s 1.004s 0.971s 10 1.05x
🌐 Redis Next.js (Turbopack) 0.048s 1.005s 0.957s 10 1.51x
🌐 MongoDB Next.js (Turbopack) 0.093s 1.008s 0.915s 10 2.91x
🐘 Postgres Nitro 0.196s (-33.7% 🟢) 1.010s (~) 0.814s 10 6.15x
🐘 Postgres Next.js (Turbopack) 0.422s 1.009s 0.587s 10 13.29x
🐘 Postgres Express 0.451s (+273.6% 🔺) 1.010s (~) 0.559s 10 14.17x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 0.879s (+9.6% 🔺) 2.288s (+3.6%) 1.408s 10 1.00x
▲ Vercel Nitro 0.958s (+2.5%) 2.208s (-5.1% 🟢) 1.250s 10 1.09x
▲ Vercel Next.js (Turbopack) 0.968s (+3.1%) 2.478s (+19.0% 🔺) 1.510s 10 1.10x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.082s 2.006s 0.923s 10 1.00x
💻 Local Nitro 1.106s (~) 2.005s (~) 0.899s 10 1.02x
🌐 Redis Next.js (Turbopack) 1.108s 2.006s 0.898s 10 1.02x
💻 Local Express 1.110s (+0.9%) 2.006s (~) 0.896s 10 1.03x
🌐 MongoDB Next.js (Turbopack) 1.307s 2.008s 0.701s 10 1.21x
🐘 Postgres Nitro 1.716s (-20.8% 🟢) 2.312s (-23.3% 🟢) 0.596s 10 1.59x
🐘 Postgres Next.js (Turbopack) 1.804s 2.012s 0.208s 10 1.67x
🐘 Postgres Express 2.372s (-3.0%) 3.014s (~) 0.642s 10 2.19x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.991s (+11.5% 🔺) 4.611s (+25.7% 🔺) 1.620s 10 1.00x
▲ Vercel Express 3.037s (+13.0% 🔺) 5.085s (+42.8% 🔺) 2.048s 10 1.02x
▲ Vercel Nitro 3.063s (+14.6% 🔺) 4.307s (+20.1% 🔺) 1.243s 10 1.02x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 10.616s 11.021s 0.405s 3 1.00x
🌐 Redis Next.js (Turbopack) 10.699s 11.022s 0.323s 3 1.01x
💻 Local Nitro 10.827s (~) 11.021s (~) 0.194s 3 1.02x
💻 Local Express 10.889s (+1.0%) 11.022s (~) 0.133s 3 1.03x
🌐 MongoDB Next.js (Turbopack) 12.252s 13.022s 0.770s 3 1.15x
🐘 Postgres Next.js (Turbopack) 14.972s 15.545s 0.573s 2 1.41x
🐘 Postgres Nitro 15.445s (-23.9% 🟢) 16.046s (-23.8% 🟢) 0.600s 2 1.45x
🐘 Postgres Express 20.238s (~) 21.055s (~) 0.818s 2 1.91x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 22.055s (~) 23.779s (+1.1%) 1.724s 2 1.00x
▲ Vercel Express 22.163s (+12.8% 🔺) 23.215s (+9.0% 🔺) 1.052s 2 1.00x
▲ Vercel Nitro 24.482s (+21.4% 🔺) 25.704s (+19.5% 🔺) 1.222s 2 1.11x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 26.889s 27.051s 0.162s 3 1.00x
💻 Local Next.js (Turbopack) 26.939s 27.051s 0.113s 3 1.00x
💻 Local Nitro 27.485s (~) 28.051s (~) 0.566s 3 1.02x
💻 Local Express 27.523s (+0.6%) 28.053s (~) 0.530s 3 1.02x
🌐 MongoDB Next.js (Turbopack) 30.578s 31.043s 0.464s 2 1.14x
🐘 Postgres Nitro 38.261s (-24.1% 🟢) 39.103s (-23.5% 🟢) 0.842s 2 1.42x
🐘 Postgres Next.js (Turbopack) 38.321s 39.097s 0.776s 2 1.43x
🐘 Postgres Express 43.548s (-12.2% 🟢) 43.606s (-13.0% 🟢) 0.057s 2 1.62x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 54.867s (+6.5% 🔺) 56.500s (+6.8% 🔺) 1.633s 2 1.00x
▲ Vercel Nitro 56.114s (+9.4% 🔺) 57.347s (+9.0% 🔺) 1.233s 2 1.02x
▲ Vercel Express 57.082s (+9.9% 🔺) 58.668s (+10.4% 🔺) 1.586s 2 1.04x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 54.355s 55.097s 0.742s 2 1.00x
💻 Local Next.js (Turbopack) 56.283s 56.608s 0.325s 2 1.04x
💻 Local Nitro 57.318s (~) 58.102s (+1.8%) 0.784s 2 1.05x
💻 Local Express 57.553s (+1.3%) 58.105s (+1.8%) 0.552s 2 1.06x
🌐 MongoDB Next.js (Turbopack) 60.920s 61.570s 0.650s 2 1.12x
🐘 Postgres Express 75.190s (-17.6% 🟢) 75.670s (-17.9% 🟢) 0.480s 2 1.38x
🐘 Postgres Nitro 75.397s (-25.0% 🟢) 76.181s (-24.7% 🟢) 0.784s 2 1.39x
🐘 Postgres Next.js (Turbopack) 95.827s 96.234s 0.407s 1 1.76x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 112.573s (+3.1%) 114.726s (+3.6%) 2.153s 1 1.00x
▲ Vercel Express 114.363s (+2.8%) 115.188s (+1.7%) 0.825s 1 1.02x
▲ Vercel Nitro 118.935s (+9.2% 🔺) 120.228s (+9.3% 🔺) 1.293s 1 1.06x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.253s 2.006s 0.754s 15 1.00x
💻 Local Next.js (Turbopack) 1.370s 2.006s 0.636s 15 1.09x
💻 Local Nitro 1.401s (+0.9%) 2.005s (~) 0.604s 15 1.12x
💻 Local Express 1.414s (+1.9%) 2.004s (~) 0.590s 15 1.13x
🐘 Postgres Next.js (Turbopack) 1.829s 2.011s 0.183s 15 1.46x
🐘 Postgres Nitro 1.832s (-20.8% 🟢) 2.013s (-33.2% 🟢) 0.181s 15 1.46x
🐘 Postgres Express 2.116s (-10.1% 🟢) 2.596s (-13.9% 🟢) 0.480s 12 1.69x
🌐 MongoDB Next.js (Turbopack) 2.152s 3.007s 0.856s 10 1.72x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.191s (+12.3% 🔺) 4.597s (+17.5% 🔺) 1.406s 7 1.00x
▲ Vercel Next.js (Turbopack) 3.274s (+16.7% 🔺) 4.724s (+23.2% 🔺) 1.450s 7 1.03x
▲ Vercel Nitro 3.522s (+28.9% 🔺) 4.906s (+34.3% 🔺) 1.383s 7 1.10x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.463s 2.916s 0.453s 11 1.00x
🌐 Redis Next.js (Turbopack) 2.505s 3.008s 0.503s 10 1.02x
💻 Local Nitro 2.613s (+3.1%) 3.007s (~) 0.394s 10 1.06x
💻 Local Express 2.628s (+6.2% 🔺) 3.007s (~) 0.380s 10 1.07x
🌐 MongoDB Next.js (Turbopack) 4.815s 5.177s 0.362s 6 1.95x
🐘 Postgres Nitro 10.804s (+44.8% 🔺) 11.365s (+37.2% 🔺) 0.561s 3 4.39x
🐘 Postgres Next.js (Turbopack) 10.904s 11.701s 0.797s 3 4.43x
🐘 Postgres Express 10.947s (+43.9% 🔺) 11.365s (+37.3% 🔺) 0.418s 3 4.44x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 4.003s (+18.4% 🔺) 5.749s (+22.8% 🔺) 1.746s 6 1.00x
▲ Vercel Next.js (Turbopack) 4.056s (+36.3% 🔺) 5.357s (+25.0% 🔺) 1.301s 6 1.01x
▲ Vercel Express 4.963s (+50.6% 🔺) 6.478s (+40.7% 🔺) 1.516s 5 1.24x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.079s 4.581s 0.502s 7 1.00x
💻 Local Next.js (Turbopack) 6.915s 7.416s 0.501s 5 1.70x
💻 Local Express 7.491s (+9.5% 🔺) 8.023s (+14.3% 🔺) 0.532s 4 1.84x
💻 Local Nitro 7.726s (+10.4% 🔺) 8.018s (+6.7% 🔺) 0.293s 4 1.89x
🌐 MongoDB Next.js (Turbopack) 9.810s 10.350s 0.540s 3 2.41x
🐘 Postgres Nitro 49.517s (+3.9%) 50.116s (+4.1%) 0.599s 1 12.14x
🐘 Postgres Express 51.550s (+3.4%) 52.113s (+3.9%) 0.563s 1 12.64x
🐘 Postgres Next.js (Turbopack) 52.174s 53.138s 0.964s 1 12.79x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.804s (-18.4% 🟢) 5.205s (-14.7% 🟢) 1.401s 6 1.00x
▲ Vercel Express 4.079s (-30.3% 🟢) 5.614s (-18.7% 🟢) 1.535s 6 1.07x
▲ Vercel Next.js (Turbopack) 4.365s (-19.8% 🟢) 5.721s (-14.0% 🟢) 1.355s 6 1.15x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.243s 2.006s 0.763s 15 1.00x
💻 Local Next.js (Turbopack) 1.406s 2.005s 0.598s 15 1.13x
💻 Local Express 1.441s (+2.3%) 2.005s (~) 0.564s 15 1.16x
💻 Local Nitro 1.449s (+2.5%) 2.005s (~) 0.557s 15 1.17x
🐘 Postgres Nitro 1.781s (-14.5% 🟢) 2.012s (-22.5% 🟢) 0.231s 15 1.43x
🐘 Postgres Next.js (Turbopack) 1.934s 2.320s 0.386s 13 1.56x
🐘 Postgres Express 2.006s (-11.2% 🟢) 2.319s (-10.6% 🟢) 0.314s 13 1.61x
🌐 MongoDB Next.js (Turbopack) 2.165s 3.008s 0.843s 10 1.74x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.860s (+4.0%) 3.649s (+6.8% 🔺) 0.789s 9 1.00x
▲ Vercel Express 3.132s (+5.1% 🔺) 4.245s (-1.2%) 1.113s 8 1.10x
▲ Vercel Nitro 4.081s (+42.3% 🔺) 5.374s (+39.7% 🔺) 1.293s 6 1.43x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.394s 3.008s 0.614s 10 1.00x
🌐 Redis Next.js (Turbopack) 2.485s 3.008s 0.523s 10 1.04x
💻 Local Nitro 2.656s (+0.9%) 3.007s (~) 0.351s 10 1.11x
💻 Local Express 2.721s (+7.5% 🔺) 3.008s (~) 0.286s 10 1.14x
🌐 MongoDB Next.js (Turbopack) 4.640s 5.176s 0.536s 6 1.94x
🐘 Postgres Nitro 10.888s (-2.2%) 11.371s (~) 0.483s 3 4.55x
🐘 Postgres Next.js (Turbopack) 11.385s 11.701s 0.316s 3 4.76x
🐘 Postgres Express 12.884s (~) 13.369s (~) 0.485s 3 5.38x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.189s (+8.9% 🔺) 4.443s (+12.1% 🔺) 1.254s 7 1.00x
▲ Vercel Express 3.299s (+7.8% 🔺) 4.507s (+3.5%) 1.208s 8 1.03x
▲ Vercel Next.js (Turbopack) 6.154s (+114.5% 🔺) 7.679s (+86.8% 🔺) 1.526s 4 1.93x

🔍 Observability: Nitro | Express | Next.js (Turbopack)

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.080s 4.725s 0.644s 7 1.00x
💻 Local Next.js (Turbopack) 7.014s 7.763s 0.750s 4 1.72x
💻 Local Nitro 7.961s (+3.6%) 8.272s (+3.2%) 0.311s 4 1.95x
💻 Local Express 8.132s (+10.0% 🔺) 9.020s (+12.5% 🔺) 0.888s 4 1.99x
🌐 MongoDB Next.js (Turbopack) 9.799s 10.349s 0.551s 3 2.40x
🐘 Postgres Nitro 49.809s (+1.1%) 50.116s (~) 0.307s 1 12.21x
🐘 Postgres Next.js (Turbopack) 51.533s 52.122s 0.589s 1 12.63x
🐘 Postgres Express 55.875s (+11.6% 🔺) 56.129s (+12.0% 🔺) 0.254s 1 13.69x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.673s (-3.2%) 5.126s (-1.7%) 1.453s 6 1.00x
▲ Vercel Next.js (Turbopack) 3.675s (-27.5% 🟢) 4.941s (-21.7% 🟢) 1.266s 7 1.00x
▲ Vercel Express 5.379s (+31.0% 🔺) 6.907s (+18.5% 🔺) 1.528s 5 1.46x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 0.124s 1.001s 0.011s 1.017s 0.892s 10 1.00x
🌐 Redis Next.js (Turbopack) 0.149s 1.000s 0.002s 1.007s 0.858s 10 1.20x
💻 Local Express 0.170s (+2.1%) 1.002s (~) 0.012s (+39.1% 🔺) 1.017s (~) 0.847s 10 1.37x
💻 Local Nitro 0.173s (+2.2%) 1.002s (~) 0.011s (+10.7% 🔺) 1.017s (~) 0.844s 10 1.39x
🌐 MongoDB Next.js (Turbopack) 0.471s 0.973s 0.002s 1.008s 0.537s 10 3.79x
🐘 Postgres Express 1.283s (-6.2% 🟢) 1.751s (+4.5%) 0.001s (~) 2.013s (~) 0.730s 10 10.33x
🐘 Postgres Nitro 1.381s (-37.1% 🟢) 1.597s (-43.9% 🟢) 0.002s (+72.7% 🔺) 1.914s (-36.5% 🟢) 0.533s 10 11.12x
🐘 Postgres Next.js (Turbopack) 1.449s 1.722s 0.002s 2.013s 0.564s 10 11.67x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.696s (+2.3%) 2.974s (-2.0%) 0.155s (~) 3.877s (+0.8%) 1.181s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.936s (+12.5% 🔺) 4.002s (+28.5% 🔺) 0.286s (+43.5% 🔺) 5.013s (+27.4% 🔺) 2.077s 10 1.09x
▲ Vercel Nitro 3.059s (+11.3% 🔺) 3.597s (+12.4% 🔺) 0.178s (-28.5% 🟢) 4.493s (+9.0% 🔺) 1.434s 10 1.13x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 11/12
🐘 Postgres Nitro 8/12
▲ Vercel Next.js (Turbopack) 5/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 10/12
Next.js (Turbopack) 💻 Local 6/12
Nitro 💻 Local 10/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 12, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 490 0 38 528
✅ 💻 Local Development 418 0 62 480
✅ 📦 Local Production 418 0 62 480
✅ 🐘 Local Postgres 418 0 62 480
✅ 🪟 Windows 45 0 3 48
❌ 🌍 Community Worlds 103 41 9 153
✅ 📋 Other 123 0 21 144
Total 2015 41 257 2313

❌ Failed Tests

🌍 Community Worlds (41 failed)

turso (41 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 44 0 4
✅ example 44 0 4
✅ express 44 0 4
✅ fastify 44 0 4
✅ hono 44 0 4
✅ nextjs-turbopack 47 0 1
✅ nextjs-webpack 47 0 1
✅ nitro 44 0 4
✅ nuxt 44 0 4
✅ sveltekit 44 0 4
✅ vite 44 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 45 0 3
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
✅ mongodb 45 0 3
✅ redis-dev 3 0 0
✅ redis 45 0 3
✅ turso-dev 3 0 0
❌ turso 4 41 3
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 41 0 7
✅ e2e-local-postgres-nest-stable 41 0 7
✅ e2e-local-prod-nest-stable 41 0 7

📋 View full workflow run

When reading stream chunks, list both .bin (current) and .json
(legacy) files so streams written before the extension change
continue to work.
Stream chunks were serialized as raw devalue text without the 'devl'
format prefix or any framing, unlike step inputs/outputs.

Core changes (serialization.ts):
- getSerializeStream: each chunk is now wrapped with
  encodeWithFormatPrefix('devl', payload) inside a length-prefixed
  frame: [4-byte big-endian length][format-prefixed payload]
- getDeserializeStream: handles both length-prefixed framed chunks
  (current) and legacy newline-delimited text (backwards compatible)
- Added 6 unit tests covering framing, round-trip, concatenation,
  splitting, and legacy fallback

World-local changes (streamer.ts):
- Stream chunk files now use .bin extension instead of .json
- readFromStream lists both .bin and .json files for backwards compat
- Updated streamer.test.ts to expect .bin extension

Split changesets: core (format + framing) and world-local (.bin extension)
@TooTallNate TooTallNate force-pushed the nate/stream-chunk-format-prefix branch from 3ee8b66 to aaaf076 Compare February 12, 2026 18:23
@TooTallNate TooTallNate requested a review from a team February 12, 2026 18:45
@TooTallNate TooTallNate changed the title Add format prefix to stream chunks and use .bin extension for chunk files Add format prefix to stream chunks and use .bin extension for chunk files (in world-local) Feb 12, 2026
@TooTallNate TooTallNate merged commit 63caf93 into main Feb 12, 2026
104 checks passed
@TooTallNate TooTallNate deleted the nate/stream-chunk-format-prefix branch February 12, 2026 19:06
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.

3 participants