CI flake: Lints

[clockwork-labs-bot]

Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.

Tests:

• Lints

Error:
Error: command ["pnpm", "lint"] exited with code 133
2026-09-11T17:04:46.2986038Z

Failed job runs:

• https://github.com/clockworklabs/SpacetimeDB/actions/runs/34625491168/job/103349528075 (Lints, attempt 1 -> 3)

Timeout detection:

• none

Context:

• none

[clockwork-labs-bot]

Diagnosis for the exact linked job/attempt: CI run 34625491168, job 103349528075, Lints, attempt 1.

This was PR #5863 (jlarabie/shard-test-suite-2) at head 9fb2b86ec3309bafd33afe260d90922677c1f190, running on ghr-github-self-hosted-ubuntu-14900k-05-spacetimedb-14-80cdafc0. Checkout, Rust/.NET/Node setup, and pnpm setup completed. The failure happened in Run ci lint while cargo ci lint ran pnpm lint.

The failing workspace package was templates/chat-react-ts. Its lint command (eslint . && prettier . --check --ignore-path ../../.prettierignore) crashed inside Node/V8:

templates/chat-react-ts lint: # Fatal error in , line 0
templates/chat-react-ts lint: # unreachable code
templates/chat-react-ts lint:  2: 0x2a229bb V8_Fatal(char const*, ...) [node]
templates/chat-react-ts lint: Failed
ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL @clockworklabs/quickstart-chat@0.0.1 lint: `eslint . && prettier . --check --ignore-path ../../.prettierignore`
Exit status 133
Error: command ["pnpm", "lint"] exited with code 133

Root cause visible in this exact attempt: Node/V8 aborted internally with fatal unreachable code while linting the chat React TS template. This is not an ESLint rule failure and not a Prettier formatting diff; the JavaScript process crashed underneath pnpm lint.

Suggested updated title: CI flake: Lints chat-react-ts lint crashes in Node/V8 unreachable code

Duplicate analysis:

• Top duplicate candidate: CI flake: v8 internal error during build #5366, the open public tracker for Node/V8 internal Fatal error ... unreachable code crashes in TypeScript build/lint workloads. This attempt has the same bare fatal headline, V8_Fatal, exit-133/SIGTRAP behavior, and TypeScript lint workload.
• Related public repeats: CI flake: Lints test-app lint crashes in Node/V8 unreachable code #5628 and CI flake: Lints #5670 are prior Lints tickets for the same Node/V8 unreachable code class during pnpm lint; CI flake: Build and test wasm bindings #5669 is the same Node/V8 fatal class during a TypeScript package build. Those closed repeats point back to CI flake: v8 internal error during build #5366 as the better canonical tracker.
• Weaker public relatives: CI flake: Node process segfault during docs pnpm build #5646/CI flake: Docs build #5749 are Node-backed docs build crashes with different signatures, so I would not mark this ticket as a duplicate of them.
• Search coverage included broad unreachable code, V8_Fatal, and narrower lint/template terms.

Top duplicate candidate: #5366. I am leaving this ticket open because #5366 is not one of the duplicate targets authorized for automatic closure by the followup request.