mirror of
https://github.com/vercel/workflow.git
synced 2026-09-14 19:59:43 +08:00
Alex Langenfeld
8789f4529b
The abort-fetch tests cancelled an in-flight fetch against external slow endpoints (postman-echo, httpbin /delay/10, tried in order). Those upstreams 5xx and return early from GH Actions runners often enough to be a recurring flake class - the tests were measuring the public internet instead of abort propagation - and heavier suite load (e.g. re-enabling e2e concurrency, #2083) makes both upstreams flake at once. fetchWithSignal now hosts its own slow endpoint: an in-process node:http server on a loopback ephemeral port that holds each response open for ~30s. The subject is unchanged - a real in-flight HTTP fetch cancelled mid-flight - with no external dependency. The 30s hold keeps regression detection honest: broken abort propagation surfaces as natural completion (ok: true) within the tests' 60s budgets. A per-workbench /api/delay route was rejected earlier because it would only exist on whichever workbench it was added to; the in-step server travels with the workflow fixture to every app. Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
Workbench
These apps are used for testing internally. Refer to Workflow SDK Examples to see some use cases and working examples.