You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 25b1873
Browse filesBrowse the repository at this point in the historyBrowse files
🤖 Settle a wedged battery command instead of hanging forever
deno bundle and the esbuild service it spawns can deadlock under
concurrent load: esbuild_client's two bounded protocol channels fill on
both sides under CPU starvation, its select loop and handler task each
park in a send the other can never drain, and both processes idle at 0%
CPU indefinitely. CI's composability job hit this on both of its runs,
hanging silently until cancelled an hour in.
Three ceilings turn that into bounded, reported failure:
- scripts/lib/retry.ts: retryStuck halts an attempt that outlives its
ceiling — tearing down the bundler pair — and runs a fresh one.
bundleClient allows three 120s attempts; only a stuck attempt retries,
a failing one still fails on the spot.
- scripts/lib/verify.ts: every battery command races a 20-minute
ceiling; a command settled by it reports (timed out) with everything
it had written, and the rest of the battery still finishes.
- ci.yml: composability gets timeout-minutes: 60 as the job backstop.
A halted build cannot orphan its esbuild service (the service exits on
pipe EOF), and a live wedge held exactly one service — the stuck
bundle's own child — so the halt-mid-bundle tests are unrelated and stay
as they are.
0 commit comments