8000 diag: A stalled claude-code download in the guest blocked FinalizeSession past the 180 s CLI timeout. · Issue #3168 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

diag: A stalled claude-code download in the guest blocked FinalizeSession past the 180 s CLI timeout. #3168

Open

Description

@minimal-foundry

Filed by norrietaylor from the diag portal.

Bundle: minimal-diag-20261105T183402Z.tar.zst

What the uploader said:

Trying to create an empty box in VS Code

warning: could not remove the unfinished session 01a1aced-96f4-708a-be40-3ba066ed05c7: the daemon did not answer within 10s; the session may still exist; run min session destroy 01a1aced-96f4-708a-be40-3ba066ed05c7 to remove it
error: FinalizeSession RPC failed: minimald-v1-FinalizeSession RPC timed out after 180s


Diagnosis

Verdict

A stalled claude-code download in the guest blocked FinalizeSession past the 180 s CLI timeout.

The guest minimald started the missing claude-code package build inside FinalizeSession at 18:16:56. The build fetches the Claude Code binary from storage.googleapis.com. That request did not complete for about 245 s. Then it failed with error sending request for url. The CLI stopped at 180 s. Its cleanup DestroySession also waited behind the same build. Later boxes finalized in about 30 ms, so the fault was transient.

Confidence

Medium. The guest log shows the stall and the transport error, but not why the request stalled. A guest network capture or a reproduction with RUST_LOG at debug for the fetcher will raise it.

Skew check

Component Version
host CLI (manifest.json) 0.7.3-rc1
provider daemon local-minvmd0 (socket-probe.json) 0.7.3-rc1, stdlib 0.0.21
guest daemon (meta.json) 0.7.3-rc1, stdlib 0.0.21
minvmd started_at vs installed marker 17:35:21Z vs 17:35:07Z

Every version agrees. No minimal process predates the install marker.

skew ruled out

Evidence

  • Guest logs/minimald.log.2026-11-05: FinalizeSession for session 01a1aced… dispatched at 18:16:56.590 and failed at 18:21:01.856 with "duration_ms":245265.
  • Same log, 18:16:56.682: starting the box's missing package builds in the box's classifier leaf for box-fcbf. No other event for that build until the failure.
  • Same log, 18:21:01.808 ERROR orchestrator: `claude-code` failed to build: other: error sending request for url (https://storage.googleapis.com/…/claude-code-releases/2.1.318/linux-arm64/claude).
  • Same log, 18:21:01.859: DestroySession failed after "duration_ms":65266 with Channel send error. The CLI was gone, which matches the "did not answer within 10s" warning.
  • Same log: FinalizeSession at 18:23:38, 18:28:37 and 18:30:27 returned ok in 27–34 ms. The claude-code build at 18:22:26 logged no error.
  • host/power.txt: the last event is a wake at 15:55Z. The Mac did not sleep during the incident.

Failure chain

  1. 18:16:56 CreateSession for box-fcbf succeeds. FinalizeSession starts the missing claude-code build.
  2. 18:16:56 onward, the HTTP fetch from storage.googleapis.com stalls in the guest.
  3. About 18:19:56 the CLI reaches its 180 s FinalizeSession timeout and sends DestroySession.
  4. DestroySession waits behind the stalled build. The CLI stops after 10 s and prints the cleanup warning.
  5. 18:21:01 the fetch fails with a transport error. Both RPCs return Channel send error.
  6. 18:22:26 a later box builds claude-code again, and later boxes start normally.

Recommended next steps

  1. Run min ls and, if box-fcbf is still listed, run min session destroy 01a1aced-96f4-708a-be40-3ba066ed05c7.
  2. Create the VS Code box again. The claude-code package is now built, so finalize will not download it.
  3. Add a bounded connect and read timeout to the package fetch path (crates/common/src/fetchers.rs, crates/op/src/sources.rs, against main).
  4. Make the CLI FinalizeSession timeout cover package builds, or report build progress, so a slow download does not look like a hung daemon.

Caveats

  • The bundle does not show why the request stalled: guest network, gvproxy, or the remote host. There is no packet-level or gvproxy log for the window.
  • The skipped config/loadouts/vscode.toml.redacted (Too many levels of symbolic links) points to a symlink loop in the user's loadout. It did not cause this failure, but the user must fix it.
  • The source citations are against main at 03e3df9, not the 0.7.3-rc1 build. I did not confirm the fetch client timeout settings.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority:should-haveShould be done. Applied by the inbox-route classifier or a human.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0