[CI Mirror] Add SurrealDB as a community world - #1696

Draft
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci
Draft

[CI Mirror] Add SurrealDB as a community world#1696
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

Internal mirror of #1579 to trigger vercel/workflow CI for an external contributor branch.

Notes

sepcntand others added 3 commits April 2, 2026 20:16
@vercel

vercelBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

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

ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreviewAug 3, 2026 11:06pm
example-nextjs-workflow-webpackReadyReadyPreviewAug 3, 2026 11:06pm
example-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-astro-workflowBuildingBuildingPreviewAug 3, 2026 11:06pm
workbench-express-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-fastify-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-hono-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nestjs-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nitro-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nuxt-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-sveltekit-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-tanstack-start-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-vite-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workflow-docsReadyReadyPreview, v0Aug 3, 2026 11:06pm
workflow-swc-playgroundReadyReadyPreviewAug 3, 2026 11:06pm
workflow-tarballsReadyReadyPreviewAug 3, 2026 11:06pm
workflow-webReadyReadyPreviewAug 3, 2026 11:06pm

@pranaygppranaygp mentioned this pull request Apr 11, 2026
3 tasks
@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@changeset-bot

changeset-botBot commented Apr 11, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: f512b21

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

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production146602391705
✅ 💻 Local Development163302271860
✅ 📦 Local Production163302271860
✅ 🐘 Local Postgres163302271860
✅ 🪟 Windows15500155
✅ 📋 Other102802121240
✅ vercel-multi-region270027
Total7575011328707
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro127028
✅ example127028
✅ express127028
✅ fastify127028
✅ hono127028
✅ nextjs-turbopack15203
✅ nextjs-webpack15203
✅ nitro127028
✅ nuxt127028
✅ sveltekit14609
✅ vite127028

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack15500

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable129026
✅ e2e-local-dev-tanstack-start-129026
✅ e2e-local-postgres-nest-stable129026
✅ e2e-local-postgres-tanstack-start-129026
✅ e2e-local-prod-nest-stable129026
✅ e2e-local-prod-tanstack-start-129026
✅ e2e-vercel-prod-nest127028
✅ e2e-vercel-prod-tanstack-start127028

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit f512b21 · Mon, 03 Aug 2026 23:20:35 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep243 (+2.1%)1309 🔴 (+22%) 🔻1345 🔴 (+24%) 🔻1375 🔴 (+13%)30
TTFSstream1255 (+396%) 🔻1320 🔴 (+21%) 🔻1352 🔴 (+22%) 🔻1440 🔴 (+29%) 🔻30
TTFShook + stream1492 (+284%) 🔻1573 🔴 (+20%) 🔻1600 🔴 (+19%) 🔻1761 🔴 (+23%) 🔻30
STSO1020 steps (inline)89 (+6.0%)115 (-25%) 💚129 (-30%) 💚211 (-38%) 💚1019
WO1020 steps115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚1
SLstream latency99 (+6.5%)142 🔴 (+6.0%)170 🔴 (+11%)199 🔴 (+8.7%)30
SOstream overhead (text)92 (-25%) 💚142 (-50%) 💚155 (-62%) 💚321 (-48%) 💚30
SOstream overhead (structured)97 (-29%) 💚146 (-40%) 💚175 (-36%) 💚337 (-20%) 💚30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 148883ms → this run 114707ms (Δ -34176ms, -23%)

 50-100 ms █░░░░┃ main 3 this 184 +181
100-150 ms ██████████████████████░┃ main 721 this 788 +67
150-200 ms ┃██████ main 226 this 34 -192
200-250 ms ┃ main 39 this 8 -31
250-300 ms ┃ main 10 this 1 -9
300-350 ms ┃ main 11 this 0 -11
350-400 ms ┃ main 4 this 1 -3
400-450 ms ┃ main 3 this 1 -2
500-550 ms ┃ main 1 this 1 +0
550-600 ms ┃ main 0 this 1 +1
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@pranaygp

pranaygp commented Apr 11, 2026

Copy link
Copy Markdown
ContributorAuthor
CleanShot 2026-04-10 at 17 47 23@2x

the surreal db setup script is failing in CI

Resolves conflicts from 651 commits of main:
- benchmark-community-world.yml: deleted upstream by the benchmark
overhaul, so the SurrealDB start/stop steps go with it.
- e2e-community-world.yml: main replaced per-service hardcoded start
steps with a generic `docker` path driven by the manifest's `services`
array, and replaced the matrix-supplied setup-command with a hardcoded
per-world case. Kept main's version, added the SurrealDB setup arm.
- create-community-worlds-matrix.mjs: kept main's version; SurrealDB now
resolves to service-type `docker` instead of a hardcoded arm.
- docs: the docs tree was split into content/worlds/{v4,v5}, so the page
moves there as surrealdb.mdx in both versions and is registered in both
meta.json files. Updated `getWorld().start?.()` to the async form and
repointed the frontmatter related links.
- worlds-manifest.json: docs path now /worlds/surrealdb.
The generic docker runner passes no container command, and
surrealdb/surrealdb:v3 exits 2 with usage output when run without
`start ...`. Added an optional `command` array to the service schema
(no-op for every other world) so the SurrealDB container actually boots.
Sign up for freeto 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

@pranaygp@sepcnt@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

[CI Mirror] Add SurrealDB as a community world - #1696

Draft
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci
Draft

[CI Mirror] Add SurrealDB as a community world#1696
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

Internal mirror of #1579 to trigger vercel/workflow CI for an external contributor branch.

Notes

sepcntand others added 3 commits April 2, 2026 20:16
@vercel

vercelBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

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

ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreviewAug 3, 2026 11:06pm
example-nextjs-workflow-webpackReadyReadyPreviewAug 3, 2026 11:06pm
example-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-astro-workflowBuildingBuildingPreviewAug 3, 2026 11:06pm
workbench-express-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-fastify-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-hono-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nestjs-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nitro-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nuxt-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-sveltekit-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-tanstack-start-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-vite-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workflow-docsReadyReadyPreview, v0Aug 3, 2026 11:06pm
workflow-swc-playgroundReadyReadyPreviewAug 3, 2026 11:06pm
workflow-tarballsReadyReadyPreviewAug 3, 2026 11:06pm
workflow-webReadyReadyPreviewAug 3, 2026 11:06pm

@pranaygppranaygp mentioned this pull request Apr 11, 2026
3 tasks
@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@changeset-bot

changeset-botBot commented Apr 11, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: f512b21

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

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production146602391705
✅ 💻 Local Development163302271860
✅ 📦 Local Production163302271860
✅ 🐘 Local Postgres163302271860
✅ 🪟 Windows15500155
✅ 📋 Other102802121240
✅ vercel-multi-region270027
Total7575011328707
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro127028
✅ example127028
✅ express127028
✅ fastify127028
✅ hono127028
✅ nextjs-turbopack15203
✅ nextjs-webpack15203
✅ nitro127028
✅ nuxt127028
✅ sveltekit14609
✅ vite127028

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack15500

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable129026
✅ e2e-local-dev-tanstack-start-129026
✅ e2e-local-postgres-nest-stable129026
✅ e2e-local-postgres-tanstack-start-129026
✅ e2e-local-prod-nest-stable129026
✅ e2e-local-prod-tanstack-start-129026
✅ e2e-vercel-prod-nest127028
✅ e2e-vercel-prod-tanstack-start127028

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit f512b21 · Mon, 03 Aug 2026 23:20:35 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep243 (+2.1%)1309 🔴 (+22%) 🔻1345 🔴 (+24%) 🔻1375 🔴 (+13%)30
TTFSstream1255 (+396%) 🔻1320 🔴 (+21%) 🔻1352 🔴 (+22%) 🔻1440 🔴 (+29%) 🔻30
TTFShook + stream1492 (+284%) 🔻1573 🔴 (+20%) 🔻1600 🔴 (+19%) 🔻1761 🔴 (+23%) 🔻30
STSO1020 steps (inline)89 (+6.0%)115 (-25%) 💚129 (-30%) 💚211 (-38%) 💚1019
WO1020 steps115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚1
SLstream latency99 (+6.5%)142 🔴 (+6.0%)170 🔴 (+11%)199 🔴 (+8.7%)30
SOstream overhead (text)92 (-25%) 💚142 (-50%) 💚155 (-62%) 💚321 (-48%) 💚30
SOstream overhead (structured)97 (-29%) 💚146 (-40%) 💚175 (-36%) 💚337 (-20%) 💚30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 148883ms → this run 114707ms (Δ -34176ms, -23%)

 50-100 ms █░░░░┃ main 3 this 184 +181
100-150 ms ██████████████████████░┃ main 721 this 788 +67
150-200 ms ┃██████ main 226 this 34 -192
200-250 ms ┃ main 39 this 8 -31
250-300 ms ┃ main 10 this 1 -9
300-350 ms ┃ main 11 this 0 -11
350-400 ms ┃ main 4 this 1 -3
400-450 ms ┃ main 3 this 1 -2
500-550 ms ┃ main 1 this 1 +0
550-600 ms ┃ main 0 this 1 +1
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@pranaygp

pranaygp commented Apr 11, 2026

Copy link
Copy Markdown
ContributorAuthor
CleanShot 2026-04-10 at 17 47 23@2x

the surreal db setup script is failing in CI

Resolves conflicts from 651 commits of main:
- benchmark-community-world.yml: deleted upstream by the benchmark
overhaul, so the SurrealDB start/stop steps go with it.
- e2e-community-world.yml: main replaced per-service hardcoded start
steps with a generic `docker` path driven by the manifest's `services`
array, and replaced the matrix-supplied setup-command with a hardcoded
per-world case. Kept main's version, added the SurrealDB setup arm.
- create-community-worlds-matrix.mjs: kept main's version; SurrealDB now
resolves to service-type `docker` instead of a hardcoded arm.
- docs: the docs tree was split into content/worlds/{v4,v5}, so the page
moves there as surrealdb.mdx in both versions and is registered in both
meta.json files. Updated `getWorld().start?.()` to the async form and
repointed the frontmatter related links.
- worlds-manifest.json: docs path now /worlds/surrealdb.
The generic docker runner passes no container command, and
surrealdb/surrealdb:v3 exits 2 with usage output when run without
`start ...`. Added an optional `command` array to the service schema
(no-op for every other world) so the SurrealDB container actually boots.
Sign up for freeto 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

@pranaygp@sepcnt@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[CI Mirror] Add SurrealDB as a community world - #1696

Draft
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci
Draft

[CI Mirror] Add SurrealDB as a community world#1696
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

Internal mirror of #1579 to trigger vercel/workflow CI for an external contributor branch.

Notes

sepcntand others added 3 commits April 2, 2026 20:16
@vercel

vercelBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

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

ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreviewAug 3, 2026 11:06pm
example-nextjs-workflow-webpackReadyReadyPreviewAug 3, 2026 11:06pm
example-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-astro-workflowBuildingBuildingPreviewAug 3, 2026 11:06pm
workbench-express-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-fastify-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-hono-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nestjs-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nitro-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nuxt-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-sveltekit-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-tanstack-start-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-vite-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workflow-docsReadyReadyPreview, v0Aug 3, 2026 11:06pm
workflow-swc-playgroundReadyReadyPreviewAug 3, 2026 11:06pm
workflow-tarballsReadyReadyPreviewAug 3, 2026 11:06pm
workflow-webReadyReadyPreviewAug 3, 2026 11:06pm

@pranaygppranaygp mentioned this pull request Apr 11, 2026
3 tasks
@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@changeset-bot

changeset-botBot commented Apr 11, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: f512b21

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

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production146602391705
✅ 💻 Local Development163302271860
✅ 📦 Local Production163302271860
✅ 🐘 Local Postgres163302271860
✅ 🪟 Windows15500155
✅ 📋 Other102802121240
✅ vercel-multi-region270027
Total7575011328707
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro127028
✅ example127028
✅ express127028
✅ fastify127028
✅ hono127028
✅ nextjs-turbopack15203
✅ nextjs-webpack15203
✅ nitro127028
✅ nuxt127028
✅ sveltekit14609
✅ vite127028

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack15500

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable129026
✅ e2e-local-dev-tanstack-start-129026
✅ e2e-local-postgres-nest-stable129026
✅ e2e-local-postgres-tanstack-start-129026
✅ e2e-local-prod-nest-stable129026
✅ e2e-local-prod-tanstack-start-129026
✅ e2e-vercel-prod-nest127028
✅ e2e-vercel-prod-tanstack-start127028

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit f512b21 · Mon, 03 Aug 2026 23:20:35 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep243 (+2.1%)1309 🔴 (+22%) 🔻1345 🔴 (+24%) 🔻1375 🔴 (+13%)30
TTFSstream1255 (+396%) 🔻1320 🔴 (+21%) 🔻1352 🔴 (+22%) 🔻1440 🔴 (+29%) 🔻30
TTFShook + stream1492 (+284%) 🔻1573 🔴 (+20%) 🔻1600 🔴 (+19%) 🔻1761 🔴 (+23%) 🔻30
STSO1020 steps (inline)89 (+6.0%)115 (-25%) 💚129 (-30%) 💚211 (-38%) 💚1019
WO1020 steps115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚1
SLstream latency99 (+6.5%)142 🔴 (+6.0%)170 🔴 (+11%)199 🔴 (+8.7%)30
SOstream overhead (text)92 (-25%) 💚142 (-50%) 💚155 (-62%) 💚321 (-48%) 💚30
SOstream overhead (structured)97 (-29%) 💚146 (-40%) 💚175 (-36%) 💚337 (-20%) 💚30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 148883ms → this run 114707ms (Δ -34176ms, -23%)

 50-100 ms █░░░░┃ main 3 this 184 +181
100-150 ms ██████████████████████░┃ main 721 this 788 +67
150-200 ms ┃██████ main 226 this 34 -192
200-250 ms ┃ main 39 this 8 -31
250-300 ms ┃ main 10 this 1 -9
300-350 ms ┃ main 11 this 0 -11
350-400 ms ┃ main 4 this 1 -3
400-450 ms ┃ main 3 this 1 -2
500-550 ms ┃ main 1 this 1 +0
550-600 ms ┃ main 0 this 1 +1
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@pranaygp

pranaygp commented Apr 11, 2026

Copy link
Copy Markdown
ContributorAuthor
CleanShot 2026-04-10 at 17 47 23@2x

the surreal db setup script is failing in CI

Resolves conflicts from 651 commits of main:
- benchmark-community-world.yml: deleted upstream by the benchmark
overhaul, so the SurrealDB start/stop steps go with it.
- e2e-community-world.yml: main replaced per-service hardcoded start
steps with a generic `docker` path driven by the manifest's `services`
array, and replaced the matrix-supplied setup-command with a hardcoded
per-world case. Kept main's version, added the SurrealDB setup arm.
- create-community-worlds-matrix.mjs: kept main's version; SurrealDB now
resolves to service-type `docker` instead of a hardcoded arm.
- docs: the docs tree was split into content/worlds/{v4,v5}, so the page
moves there as surrealdb.mdx in both versions and is registered in both
meta.json files. Updated `getWorld().start?.()` to the async form and
repointed the frontmatter related links.
- worlds-manifest.json: docs path now /worlds/surrealdb.
The generic docker runner passes no container command, and
surrealdb/surrealdb:v3 exits 2 with usage output when run without
`start ...`. Added an optional `command` array to the service schema
(no-op for every other world) so the SurrealDB container actually boots.
Sign up for freeto 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

@pranaygp@sepcnt@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[CI Mirror] Add SurrealDB as a community world - #1696

Draft
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci
Draft

[CI Mirror] Add SurrealDB as a community world#1696
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

Internal mirror of #1579 to trigger vercel/workflow CI for an external contributor branch.

Notes

sepcntand others added 3 commits April 2, 2026 20:16
@vercel

vercelBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

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

ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreviewAug 3, 2026 11:06pm
example-nextjs-workflow-webpackReadyReadyPreviewAug 3, 2026 11:06pm
example-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-astro-workflowBuildingBuildingPreviewAug 3, 2026 11:06pm
workbench-express-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-fastify-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-hono-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nestjs-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nitro-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nuxt-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-sveltekit-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-tanstack-start-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-vite-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workflow-docsReadyReadyPreview, v0Aug 3, 2026 11:06pm
workflow-swc-playgroundReadyReadyPreviewAug 3, 2026 11:06pm
workflow-tarballsReadyReadyPreviewAug 3, 2026 11:06pm
workflow-webReadyReadyPreviewAug 3, 2026 11:06pm

@pranaygppranaygp mentioned this pull request Apr 11, 2026
3 tasks
@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@changeset-bot

changeset-botBot commented Apr 11, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: f512b21

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

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production146602391705
✅ 💻 Local Development163302271860
✅ 📦 Local Production163302271860
✅ 🐘 Local Postgres163302271860
✅ 🪟 Windows15500155
✅ 📋 Other102802121240
✅ vercel-multi-region270027
Total7575011328707
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro127028
✅ example127028
✅ express127028
✅ fastify127028
✅ hono127028
✅ nextjs-turbopack15203
✅ nextjs-webpack15203
✅ nitro127028
✅ nuxt127028
✅ sveltekit14609
✅ vite127028

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack15500

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable129026
✅ e2e-local-dev-tanstack-start-129026
✅ e2e-local-postgres-nest-stable129026
✅ e2e-local-postgres-tanstack-start-129026
✅ e2e-local-prod-nest-stable129026
✅ e2e-local-prod-tanstack-start-129026
✅ e2e-vercel-prod-nest127028
✅ e2e-vercel-prod-tanstack-start127028

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit f512b21 · Mon, 03 Aug 2026 23:20:35 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep243 (+2.1%)1309 🔴 (+22%) 🔻1345 🔴 (+24%) 🔻1375 🔴 (+13%)30
TTFSstream1255 (+396%) 🔻1320 🔴 (+21%) 🔻1352 🔴 (+22%) 🔻1440 🔴 (+29%) 🔻30
TTFShook + stream1492 (+284%) 🔻1573 🔴 (+20%) 🔻1600 🔴 (+19%) 🔻1761 🔴 (+23%) 🔻30
STSO1020 steps (inline)89 (+6.0%)115 (-25%) 💚129 (-30%) 💚211 (-38%) 💚1019
WO1020 steps115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚1
SLstream latency99 (+6.5%)142 🔴 (+6.0%)170 🔴 (+11%)199 🔴 (+8.7%)30
SOstream overhead (text)92 (-25%) 💚142 (-50%) 💚155 (-62%) 💚321 (-48%) 💚30
SOstream overhead (structured)97 (-29%) 💚146 (-40%) 💚175 (-36%) 💚337 (-20%) 💚30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 148883ms → this run 114707ms (Δ -34176ms, -23%)

 50-100 ms █░░░░┃ main 3 this 184 +181
100-150 ms ██████████████████████░┃ main 721 this 788 +67
150-200 ms ┃██████ main 226 this 34 -192
200-250 ms ┃ main 39 this 8 -31
250-300 ms ┃ main 10 this 1 -9
300-350 ms ┃ main 11 this 0 -11
350-400 ms ┃ main 4 this 1 -3
400-450 ms ┃ main 3 this 1 -2
500-550 ms ┃ main 1 this 1 +0
550-600 ms ┃ main 0 this 1 +1
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@pranaygp

pranaygp commented Apr 11, 2026

Copy link
Copy Markdown
ContributorAuthor
CleanShot 2026-04-10 at 17 47 23@2x

the surreal db setup script is failing in CI

Resolves conflicts from 651 commits of main:
- benchmark-community-world.yml: deleted upstream by the benchmark
overhaul, so the SurrealDB start/stop steps go with it.
- e2e-community-world.yml: main replaced per-service hardcoded start
steps with a generic `docker` path driven by the manifest's `services`
array, and replaced the matrix-supplied setup-command with a hardcoded
per-world case. Kept main's version, added the SurrealDB setup arm.
- create-community-worlds-matrix.mjs: kept main's version; SurrealDB now
resolves to service-type `docker` instead of a hardcoded arm.
- docs: the docs tree was split into content/worlds/{v4,v5}, so the page
moves there as surrealdb.mdx in both versions and is registered in both
meta.json files. Updated `getWorld().start?.()` to the async form and
repointed the frontmatter related links.
- worlds-manifest.json: docs path now /worlds/surrealdb.
The generic docker runner passes no container command, and
surrealdb/surrealdb:v3 exits 2 with usage output when run without
`start ...`. Added an optional `command` array to the service schema
(no-op for every other world) so the SurrealDB container actually boots.
Sign up for freeto 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

@pranaygp@sepcnt@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

[CI Mirror] Add SurrealDB as a community world - #1696

Draft
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci
Draft

[CI Mirror] Add SurrealDB as a community world#1696
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

Internal mirror of #1579 to trigger vercel/workflow CI for an external contributor branch.

Notes

sepcntand others added 3 commits April 2, 2026 20:16
@vercel

vercelBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

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

ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreviewAug 3, 2026 11:06pm
example-nextjs-workflow-webpackReadyReadyPreviewAug 3, 2026 11:06pm
example-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-astro-workflowBuildingBuildingPreviewAug 3, 2026 11:06pm
workbench-express-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-fastify-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-hono-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nestjs-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nitro-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nuxt-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-sveltekit-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-tanstack-start-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-vite-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workflow-docsReadyReadyPreview, v0Aug 3, 2026 11:06pm
workflow-swc-playgroundReadyReadyPreviewAug 3, 2026 11:06pm
workflow-tarballsReadyReadyPreviewAug 3, 2026 11:06pm
workflow-webReadyReadyPreviewAug 3, 2026 11:06pm

@pranaygppranaygp mentioned this pull request Apr 11, 2026
3 tasks
@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@changeset-bot

changeset-botBot commented Apr 11, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: f512b21

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

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production146602391705
✅ 💻 Local Development163302271860
✅ 📦 Local Production163302271860
✅ 🐘 Local Postgres163302271860
✅ 🪟 Windows15500155
✅ 📋 Other102802121240
✅ vercel-multi-region270027
Total7575011328707
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro127028
✅ example127028
✅ express127028
✅ fastify127028
✅ hono127028
✅ nextjs-turbopack15203
✅ nextjs-webpack15203
✅ nitro127028
✅ nuxt127028
✅ sveltekit14609
✅ vite127028

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack15500

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable129026
✅ e2e-local-dev-tanstack-start-129026
✅ e2e-local-postgres-nest-stable129026
✅ e2e-local-postgres-tanstack-start-129026
✅ e2e-local-prod-nest-stable129026
✅ e2e-local-prod-tanstack-start-129026
✅ e2e-vercel-prod-nest127028
✅ e2e-vercel-prod-tanstack-start127028

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit f512b21 · Mon, 03 Aug 2026 23:20:35 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep243 (+2.1%)1309 🔴 (+22%) 🔻1345 🔴 (+24%) 🔻1375 🔴 (+13%)30
TTFSstream1255 (+396%) 🔻1320 🔴 (+21%) 🔻1352 🔴 (+22%) 🔻1440 🔴 (+29%) 🔻30
TTFShook + stream1492 (+284%) 🔻1573 🔴 (+20%) 🔻1600 🔴 (+19%) 🔻1761 🔴 (+23%) 🔻30
STSO1020 steps (inline)89 (+6.0%)115 (-25%) 💚129 (-30%) 💚211 (-38%) 💚1019
WO1020 steps115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚1
SLstream latency99 (+6.5%)142 🔴 (+6.0%)170 🔴 (+11%)199 🔴 (+8.7%)30
SOstream overhead (text)92 (-25%) 💚142 (-50%) 💚155 (-62%) 💚321 (-48%) 💚30
SOstream overhead (structured)97 (-29%) 💚146 (-40%) 💚175 (-36%) 💚337 (-20%) 💚30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 148883ms → this run 114707ms (Δ -34176ms, -23%)

 50-100 ms █░░░░┃ main 3 this 184 +181
100-150 ms ██████████████████████░┃ main 721 this 788 +67
150-200 ms ┃██████ main 226 this 34 -192
200-250 ms ┃ main 39 this 8 -31
250-300 ms ┃ main 10 this 1 -9
300-350 ms ┃ main 11 this 0 -11
350-400 ms ┃ main 4 this 1 -3
400-450 ms ┃ main 3 this 1 -2
500-550 ms ┃ main 1 this 1 +0
550-600 ms ┃ main 0 this 1 +1
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@pranaygp

pranaygp commented Apr 11, 2026

Copy link
Copy Markdown
ContributorAuthor
CleanShot 2026-04-10 at 17 47 23@2x

the surreal db setup script is failing in CI

Resolves conflicts from 651 commits of main:
- benchmark-community-world.yml: deleted upstream by the benchmark
overhaul, so the SurrealDB start/stop steps go with it.
- e2e-community-world.yml: main replaced per-service hardcoded start
steps with a generic `docker` path driven by the manifest's `services`
array, and replaced the matrix-supplied setup-command with a hardcoded
per-world case. Kept main's version, added the SurrealDB setup arm.
- create-community-worlds-matrix.mjs: kept main's version; SurrealDB now
resolves to service-type `docker` instead of a hardcoded arm.
- docs: the docs tree was split into content/worlds/{v4,v5}, so the page
moves there as surrealdb.mdx in both versions and is registered in both
meta.json files. Updated `getWorld().start?.()` to the async form and
repointed the frontmatter related links.
- worlds-manifest.json: docs path now /worlds/surrealdb.
The generic docker runner passes no container command, and
surrealdb/surrealdb:v3 exits 2 with usage output when run without
`start ...`. Added an optional `command` array to the service schema
(no-op for every other world) so the SurrealDB container actually boots.
Sign up for freeto 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

@pranaygp@sepcnt@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[CI Mirror] Add SurrealDB as a community world - #1696

Draft
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci
Draft

[CI Mirror] Add SurrealDB as a community world#1696
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

Internal mirror of #1579 to trigger vercel/workflow CI for an external contributor branch.

Notes

sepcntand others added 3 commits April 2, 2026 20:16
@vercel

vercelBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

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

ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreviewAug 3, 2026 11:06pm
example-nextjs-workflow-webpackReadyReadyPreviewAug 3, 2026 11:06pm
example-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-astro-workflowBuildingBuildingPreviewAug 3, 2026 11:06pm
workbench-express-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-fastify-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-hono-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nestjs-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nitro-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nuxt-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-sveltekit-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-tanstack-start-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-vite-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workflow-docsReadyReadyPreview, v0Aug 3, 2026 11:06pm
workflow-swc-playgroundReadyReadyPreviewAug 3, 2026 11:06pm
workflow-tarballsReadyReadyPreviewAug 3, 2026 11:06pm
workflow-webReadyReadyPreviewAug 3, 2026 11:06pm

@pranaygppranaygp mentioned this pull request Apr 11, 2026
3 tasks
@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@changeset-bot

changeset-botBot commented Apr 11, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: f512b21

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

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production146602391705
✅ 💻 Local Development163302271860
✅ 📦 Local Production163302271860
✅ 🐘 Local Postgres163302271860
✅ 🪟 Windows15500155
✅ 📋 Other102802121240
✅ vercel-multi-region270027
Total7575011328707
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro127028
✅ example127028
✅ express127028
✅ fastify127028
✅ hono127028
✅ nextjs-turbopack15203
✅ nextjs-webpack15203
✅ nitro127028
✅ nuxt127028
✅ sveltekit14609
✅ vite127028

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack15500

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable129026
✅ e2e-local-dev-tanstack-start-129026
✅ e2e-local-postgres-nest-stable129026
✅ e2e-local-postgres-tanstack-start-129026
✅ e2e-local-prod-nest-stable129026
✅ e2e-local-prod-tanstack-start-129026
✅ e2e-vercel-prod-nest127028
✅ e2e-vercel-prod-tanstack-start127028

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit f512b21 · Mon, 03 Aug 2026 23:20:35 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep243 (+2.1%)1309 🔴 (+22%) 🔻1345 🔴 (+24%) 🔻1375 🔴 (+13%)30
TTFSstream1255 (+396%) 🔻1320 🔴 (+21%) 🔻1352 🔴 (+22%) 🔻1440 🔴 (+29%) 🔻30
TTFShook + stream1492 (+284%) 🔻1573 🔴 (+20%) 🔻1600 🔴 (+19%) 🔻1761 🔴 (+23%) 🔻30
STSO1020 steps (inline)89 (+6.0%)115 (-25%) 💚129 (-30%) 💚211 (-38%) 💚1019
WO1020 steps115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚1
SLstream latency99 (+6.5%)142 🔴 (+6.0%)170 🔴 (+11%)199 🔴 (+8.7%)30
SOstream overhead (text)92 (-25%) 💚142 (-50%) 💚155 (-62%) 💚321 (-48%) 💚30
SOstream overhead (structured)97 (-29%) 💚146 (-40%) 💚175 (-36%) 💚337 (-20%) 💚30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 148883ms → this run 114707ms (Δ -34176ms, -23%)

 50-100 ms █░░░░┃ main 3 this 184 +181
100-150 ms ██████████████████████░┃ main 721 this 788 +67
150-200 ms ┃██████ main 226 this 34 -192
200-250 ms ┃ main 39 this 8 -31
250-300 ms ┃ main 10 this 1 -9
300-350 ms ┃ main 11 this 0 -11
350-400 ms ┃ main 4 this 1 -3
400-450 ms ┃ main 3 this 1 -2
500-550 ms ┃ main 1 this 1 +0
550-600 ms ┃ main 0 this 1 +1
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@pranaygp

pranaygp commented Apr 11, 2026

Copy link
Copy Markdown
ContributorAuthor
CleanShot 2026-04-10 at 17 47 23@2x

the surreal db setup script is failing in CI

Resolves conflicts from 651 commits of main:
- benchmark-community-world.yml: deleted upstream by the benchmark
overhaul, so the SurrealDB start/stop steps go with it.
- e2e-community-world.yml: main replaced per-service hardcoded start
steps with a generic `docker` path driven by the manifest's `services`
array, and replaced the matrix-supplied setup-command with a hardcoded
per-world case. Kept main's version, added the SurrealDB setup arm.
- create-community-worlds-matrix.mjs: kept main's version; SurrealDB now
resolves to service-type `docker` instead of a hardcoded arm.
- docs: the docs tree was split into content/worlds/{v4,v5}, so the page
moves there as surrealdb.mdx in both versions and is registered in both
meta.json files. Updated `getWorld().start?.()` to the async form and
repointed the frontmatter related links.
- worlds-manifest.json: docs path now /worlds/surrealdb.
The generic docker runner passes no container command, and
surrealdb/surrealdb:v3 exits 2 with usage output when run without
`start ...`. Added an optional `command` array to the service schema
(no-op for every other world) so the SurrealDB container actually boots.
Sign up for freeto 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

@pranaygp@sepcnt@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[CI Mirror] Add SurrealDB as a community world - #1696

Draft
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci
Draft

[CI Mirror] Add SurrealDB as a community world#1696
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

Internal mirror of #1579 to trigger vercel/workflow CI for an external contributor branch.

Notes

sepcntand others added 3 commits April 2, 2026 20:16
@vercel

vercelBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

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

ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreviewAug 3, 2026 11:06pm
example-nextjs-workflow-webpackReadyReadyPreviewAug 3, 2026 11:06pm
example-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-astro-workflowBuildingBuildingPreviewAug 3, 2026 11:06pm
workbench-express-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-fastify-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-hono-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nestjs-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nitro-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nuxt-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-sveltekit-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-tanstack-start-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-vite-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workflow-docsReadyReadyPreview, v0Aug 3, 2026 11:06pm
workflow-swc-playgroundReadyReadyPreviewAug 3, 2026 11:06pm
workflow-tarballsReadyReadyPreviewAug 3, 2026 11:06pm
workflow-webReadyReadyPreviewAug 3, 2026 11:06pm

@pranaygppranaygp mentioned this pull request Apr 11, 2026
3 tasks
@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@changeset-bot

changeset-botBot commented Apr 11, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: f512b21

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

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production146602391705
✅ 💻 Local Development163302271860
✅ 📦 Local Production163302271860
✅ 🐘 Local Postgres163302271860
✅ 🪟 Windows15500155
✅ 📋 Other102802121240
✅ vercel-multi-region270027
Total7575011328707
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro127028
✅ example127028
✅ express127028
✅ fastify127028
✅ hono127028
✅ nextjs-turbopack15203
✅ nextjs-webpack15203
✅ nitro127028
✅ nuxt127028
✅ sveltekit14609
✅ vite127028

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack15500

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable129026
✅ e2e-local-dev-tanstack-start-129026
✅ e2e-local-postgres-nest-stable129026
✅ e2e-local-postgres-tanstack-start-129026
✅ e2e-local-prod-nest-stable129026
✅ e2e-local-prod-tanstack-start-129026
✅ e2e-vercel-prod-nest127028
✅ e2e-vercel-prod-tanstack-start127028

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit f512b21 · Mon, 03 Aug 2026 23:20:35 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep243 (+2.1%)1309 🔴 (+22%) 🔻1345 🔴 (+24%) 🔻1375 🔴 (+13%)30
TTFSstream1255 (+396%) 🔻1320 🔴 (+21%) 🔻1352 🔴 (+22%) 🔻1440 🔴 (+29%) 🔻30
TTFShook + stream1492 (+284%) 🔻1573 🔴 (+20%) 🔻1600 🔴 (+19%) 🔻1761 🔴 (+23%) 🔻30
STSO1020 steps (inline)89 (+6.0%)115 (-25%) 💚129 (-30%) 💚211 (-38%) 💚1019
WO1020 steps115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚1
SLstream latency99 (+6.5%)142 🔴 (+6.0%)170 🔴 (+11%)199 🔴 (+8.7%)30
SOstream overhead (text)92 (-25%) 💚142 (-50%) 💚155 (-62%) 💚321 (-48%) 💚30
SOstream overhead (structured)97 (-29%) 💚146 (-40%) 💚175 (-36%) 💚337 (-20%) 💚30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 148883ms → this run 114707ms (Δ -34176ms, -23%)

 50-100 ms █░░░░┃ main 3 this 184 +181
100-150 ms ██████████████████████░┃ main 721 this 788 +67
150-200 ms ┃██████ main 226 this 34 -192
200-250 ms ┃ main 39 this 8 -31
250-300 ms ┃ main 10 this 1 -9
300-350 ms ┃ main 11 this 0 -11
350-400 ms ┃ main 4 this 1 -3
400-450 ms ┃ main 3 this 1 -2
500-550 ms ┃ main 1 this 1 +0
550-600 ms ┃ main 0 this 1 +1
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@pranaygp

pranaygp commented Apr 11, 2026

Copy link
Copy Markdown
ContributorAuthor
CleanShot 2026-04-10 at 17 47 23@2x

the surreal db setup script is failing in CI

Resolves conflicts from 651 commits of main:
- benchmark-community-world.yml: deleted upstream by the benchmark
overhaul, so the SurrealDB start/stop steps go with it.
- e2e-community-world.yml: main replaced per-service hardcoded start
steps with a generic `docker` path driven by the manifest's `services`
array, and replaced the matrix-supplied setup-command with a hardcoded
per-world case. Kept main's version, added the SurrealDB setup arm.
- create-community-worlds-matrix.mjs: kept main's version; SurrealDB now
resolves to service-type `docker` instead of a hardcoded arm.
- docs: the docs tree was split into content/worlds/{v4,v5}, so the page
moves there as surrealdb.mdx in both versions and is registered in both
meta.json files. Updated `getWorld().start?.()` to the async form and
repointed the frontmatter related links.
- worlds-manifest.json: docs path now /worlds/surrealdb.
The generic docker runner passes no container command, and
surrealdb/surrealdb:v3 exits 2 with usage output when run without
`start ...`. Added an optional `command` array to the service schema
(no-op for every other world) so the SurrealDB container actually boots.
Sign up for freeto 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

@pranaygp@sepcnt@VaguelySerious
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

[CI Mirror] Add SurrealDB as a community world - #1696

Draft
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci
Draft

[CI Mirror] Add SurrealDB as a community world#1696
pranaygp wants to merge 5 commits into
mainfrom
pranaygp/codex/pr-1579-ci

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

Internal mirror of #1579 to trigger vercel/workflow CI for an external contributor branch.

Notes

sepcntand others added 3 commits April 2, 2026 20:16
@vercel

vercelBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

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

ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreviewAug 3, 2026 11:06pm
example-nextjs-workflow-webpackReadyReadyPreviewAug 3, 2026 11:06pm
example-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-astro-workflowBuildingBuildingPreviewAug 3, 2026 11:06pm
workbench-express-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-fastify-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-hono-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nestjs-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nitro-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-nuxt-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-sveltekit-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-tanstack-start-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workbench-vite-workflowReadyReadyPreviewAug 3, 2026 11:06pm
workflow-docsReadyReadyPreview, v0Aug 3, 2026 11:06pm
workflow-swc-playgroundReadyReadyPreviewAug 3, 2026 11:06pm
workflow-tarballsReadyReadyPreviewAug 3, 2026 11:06pm
workflow-webReadyReadyPreviewAug 3, 2026 11:06pm

@pranaygppranaygp mentioned this pull request Apr 11, 2026
3 tasks
@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@changeset-bot

changeset-botBot commented Apr 11, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: f512b21

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

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production146602391705
✅ 💻 Local Development163302271860
✅ 📦 Local Production163302271860
✅ 🐘 Local Postgres163302271860
✅ 🪟 Windows15500155
✅ 📋 Other102802121240
✅ vercel-multi-region270027
Total7575011328707
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro127028
✅ example127028
✅ express127028
✅ fastify127028
✅ hono127028
✅ nextjs-turbopack15203
✅ nextjs-webpack15203
✅ nitro127028
✅ nuxt127028
✅ sveltekit14609
✅ vite127028

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable129026
✅ express-stable129026
✅ fastify-stable129026
✅ hono-stable129026
✅ nextjs-turbopack-canary136019
✅ nextjs-turbopack-stable15500
✅ nextjs-webpack-canary136019
✅ nextjs-webpack-stable15500
✅ nitro-stable129026
✅ nuxt-stable129026
✅ sveltekit-stable14807
✅ vite-stable129026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack15500

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable129026
✅ e2e-local-dev-tanstack-start-129026
✅ e2e-local-postgres-nest-stable129026
✅ e2e-local-postgres-tanstack-start-129026
✅ e2e-local-prod-nest-stable129026
✅ e2e-local-prod-tanstack-start-129026
✅ e2e-vercel-prod-nest127028
✅ e2e-vercel-prod-tanstack-start127028

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@github-actions

github-actionsBot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit f512b21 · Mon, 03 Aug 2026 23:20:35 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep243 (+2.1%)1309 🔴 (+22%) 🔻1345 🔴 (+24%) 🔻1375 🔴 (+13%)30
TTFSstream1255 (+396%) 🔻1320 🔴 (+21%) 🔻1352 🔴 (+22%) 🔻1440 🔴 (+29%) 🔻30
TTFShook + stream1492 (+284%) 🔻1573 🔴 (+20%) 🔻1600 🔴 (+19%) 🔻1761 🔴 (+23%) 🔻30
STSO1020 steps (inline)89 (+6.0%)115 (-25%) 💚129 (-30%) 💚211 (-38%) 💚1019
WO1020 steps115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚115996 (-24%) 💚1
SLstream latency99 (+6.5%)142 🔴 (+6.0%)170 🔴 (+11%)199 🔴 (+8.7%)30
SOstream overhead (text)92 (-25%) 💚142 (-50%) 💚155 (-62%) 💚321 (-48%) 💚30
SOstream overhead (structured)97 (-29%) 💚146 (-40%) 💚175 (-36%) 💚337 (-20%) 💚30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 148883ms → this run 114707ms (Δ -34176ms, -23%)

 50-100 ms █░░░░┃ main 3 this 184 +181
100-150 ms ██████████████████████░┃ main 721 this 788 +67
150-200 ms ┃██████ main 226 this 34 -192
200-250 ms ┃ main 39 this 8 -31
250-300 ms ┃ main 10 this 1 -9
300-350 ms ┃ main 11 this 0 -11
350-400 ms ┃ main 4 this 1 -3
400-450 ms ┃ main 3 this 1 -2
500-550 ms ┃ main 1 this 1 +0
550-600 ms ┃ main 0 this 1 +1
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@pranaygp

Copy link
Copy Markdown
ContributorAuthor

Crosslink: this draft PR mirrors external contributor PR #1579 only to trigger internal CI. If checks pass here, merge #1579 and close this mirror.

@pranaygp

pranaygp commented Apr 11, 2026

Copy link
Copy Markdown
ContributorAuthor
CleanShot 2026-04-10 at 17 47 23@2x

the surreal db setup script is failing in CI

Resolves conflicts from 651 commits of main:
- benchmark-community-world.yml: deleted upstream by the benchmark
overhaul, so the SurrealDB start/stop steps go with it.
- e2e-community-world.yml: main replaced per-service hardcoded start
steps with a generic `docker` path driven by the manifest's `services`
array, and replaced the matrix-supplied setup-command with a hardcoded
per-world case. Kept main's version, added the SurrealDB setup arm.
- create-community-worlds-matrix.mjs: kept main's version; SurrealDB now
resolves to service-type `docker` instead of a hardcoded arm.
- docs: the docs tree was split into content/worlds/{v4,v5}, so the page
moves there as surrealdb.mdx in both versions and is registered in both
meta.json files. Updated `getWorld().start?.()` to the async form and
repointed the frontmatter related links.
- worlds-manifest.json: docs path now /worlds/surrealdb.
The generic docker runner passes no container command, and
surrealdb/surrealdb:v3 exits 2 with usage output when run without
`start ...`. Added an optional `command` array to the service schema
(no-op for every other world) so the SurrealDB container actually boots.
Sign up for freeto 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

@pranaygp@sepcnt@VaguelySerious