CI flake: Lints

[clockwork-labs-bot]

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

Tests:

• Lints

Error:
thread 'main' (20124) panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/v8-145.0.0/build.rs:669:3:
assertion failed: status.success()

Failed job runs:

• https://github.com/clockworklabs/SpacetimeDB/actions/runs/31634062242/job/94239866939 (Lints, attempt 1 -> 2)

Timeout detection:

• none

Context:

• none

[clockwork-labs-bot]

Diagnosis for the linked failed attempt only: run 31634062242, job 94239866939, Lints, attempt 1.

This was PR #5732 (bot/docs-submodules-dot-separator) at head bbd66e0360b7427fdfea1a981be8e61b2cf449ea / merge ref 78c4b6caa52b57f6e376c13cd07cf624f7b4f363, on runner ghr-github-self-hosted-ubuntu-14900k-02-spacetimedb-14-f76932ca. Setup, checkout, Rust, .NET, Node, pnpm, and dependency cache restore completed. The failure happened in Run ci lint while Cargo was checking the workspace.

Failure signature:

error: failed to run custom build command for `v8 v145.0.0`
Downloading ... librusty_v8_release_x86_64-unknown-linux-gnu.a.gz...Python downloader failed, trying with curl.
http.client.RemoteDisconnected: Remote end closed connection without response
thread 'main' ... v8-145.0.0/build.rs:669:3:
assertion failed: status.success()

Root cause: the v8 crate build script could not fetch the prebuilt rusty_v8 archive from the GitHub release. The Python downloader got a remote disconnect, the curl fallback also did not return success, and build.rs panicked on that failed download status. This is CI/network/artifact-fetch instability during dependency setup, not a lint finding or source compile error. The rerun later passed.

Suggested updated title: CI flake: v8 build script fails downloading rusty_v8 archive

Duplicate analysis:

• CI flake: Test Suite #5750 is the same failure mechanism in the same CI run family: v8 v145.0.0 build script, librusty_v8_release_x86_64-unknown-linux-gnu.a.gz, RemoteDisconnected, then assertion failed: status.success().
• CI flake: v8 internal error during build #5366 is related only at the broad Node/V8 level. It tracks Node/V8 internal unreachable code crashes during TypeScript builds, not rusty_v8 archive download failures, so I would not mark this as a duplicate of CI flake: v8 internal error during build #5366.
• I searched broad and narrow terms including RemoteDisconnected, Remote end closed connection, librusty_v8_release_x86_64-unknown-linux-gnu.a.gz, rusty_v8, failed to run custom build command v8, and status.success v8. Open searches did not find an older close duplicate. Some later closed-issue fallback searches hit GitHub search 403 rate limits, so the duplicate search is incomplete and I am not claiming that no older closed duplicate exists.

Top duplicate candidate: none I would close against automatically. #5750 is an exact same-family ticket, but it is another new ticket from this batch, and no allowed duplicate target was found.