Claude Opus 4.8
7b17e05826
All checks were successful
CD / Build and push images (push) Successful in 56s
CI / Lint, typecheck, test (push) Successful in 1m56s
CI / Auth e2e pack (push) Successful in 2m25s
CI / Build container images (push) Has been skipped
CD / Deploy to Test (push) Successful in 8s
CD / Smoke tests against Test (push) Successful in 1m12s
CD / Promote to Int (push) Successful in 11s
Root cause of the CI-only Auth-e2e failure (found in the runner log): the offline pack started with `connect ECONNREFUSED :5173` — the e2e static web server had already exited. Its `/collab` WebSocket proxy attached an 'error' handler to the upstream socket but not to the client socket, so a WebSocket dropped abruptly (a context closing at the end of the collab pack, or the offline toggle) raised an unhandled 'error' → uncaught exception → the whole test server crashed, failing the next pack. It only reproduced on the CI runner (Linux/Node 22 emits 'error'; local macOS/Node 26 emitted 'close'). Handle 'error' on the client socket too, and add a last-resort `uncaughtException` guard so this throwaway test server can never be taken down mid-run by a stray socket error. Verified locally by running the collab and offline packs back-to-back against a single server process. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PGdhRiwU1WRL4XxJfZYipY |
||
|---|---|---|
| .. | ||
| e2e-static-server.mjs | ||
| i18n-check.mjs | ||