8000 D3599 — min box spec reports a minimal.toml that does not load as a spec it cannot show, and a start keeps "Cannot start the box" · Issue #3601 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

D3599 — min box spec reports a minimal.toml that does not load as a spec it cannot show, and a start keeps "Cannot start the box" #3601

Closed

Description

@norrietaylor

Task

Source: #3599

Plan block
### D3599 — min box spec reports a minimal.toml that does not load as a spec it cannot show, and a start keeps "Cannot start the box"
  kind: task
  size: S
  est: 45 code, 60 tests
  executor: agent
  origin: bug
  layers:
    - spec:
      - crates/minimal/src/cmd/box_spec.rs: adds SpecFileInvalid (exit 3, text: Cannot show the spec: the project's minimal.toml does not load: {error}) and box_spec_to maps every ProjectFileInvalid to it
      - crates/minimal/src/cmd/mod.rs: re-exports SpecFileInvalid from box_spec so that main.rs can read it
      - crates/minimal/src/main.rs: failure_exit_code gives exit 3 for SpecFileInvalid, and a new test pins the spec text and keeps the start text in invalid_project_file_prints_toml_error_once
      - crates/minimal/src/tests.rs: box spec tests (spec_project_error and the downcasts near lines 17925, 18595, 18612) downcast SpecFileInvalid and check that the text does not say Cannot start the box
      test: cargo test -p minimal invalid_project_file_prints_toml_error_once
      test: cargo test -p minimal invalid_project_file_for_box_spec_says_spec_cannot_show
  proof: With a minimal.toml that has mode = "host_ip" under [defaults.session.network], min box spec prints that the spec cannot be shown because the project's minimal.toml does not load, exits 3, and min box start still prints Cannot start the box.

Activity

  1. norrietaylor commented on Nov 18, 2026

    @norrietaylor
    MemberAuthor

    /implement

  2. added
    bugSomething isn't working
    kind:taskA task the plan skill rendered; the body carries ## Task
    on Nov 18, 2026
  3. minimal-foundry commented on Nov 18, 2026

    @minimal-foundry
    Contributor

    That /implement is queued, not refused. 4 follow-up coders are in flight, and 3 is the most that run at once, so no coder started. 7 queued commands are ahead of it. The runtime starts queued follow-up coders oldest first as room frees, looking every ten minutes, and refuses one still waiting after 14 days.

    Nothing to type again: the command gets a rocket when its coder starts, or a refusal that names the reason. /implement stop takes it off the queue.

  4. minimal-foundry commented on Nov 19, 2026

    @minimal-foundry
    Contributor

    Pull request #3618 is open for D3599.

    branch agent/3601-min-box-spec-reports-a-minimal-toml-that-does-no

    test exit tail
    cargo test -p minimal invalid_project_file_prints_toml_error_once 0 ed; 0 ignored; 0 measured; 1026 filtered out; finished in 0.00s running 2 tests test tests::invalid_project_file_prints_toml_error_once_for_io ... ok test tests::invalid_project_file_prints_toml_error_once ... ok test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 40 filtered out; finishe
    cargo test -p minimal invalid_project_file_for_box_spec_says_spec_cannot_show 0 running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 1026 filtered out; finished in 0.00s running 1 test test tests::invalid_project_file_for_box_spec_says_spec_cannot_show ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 41 filtered out; finished in 0.0

    Verify min task run agent-verify: exit 100 — _id": "238f17aa6b945688", "span_id": "608015830b9a3296", "trace_id": "0af7651916cd43dd8448eb211c803111", }, parent: None, closed: true, }, LoggedSpan { name: "session.message", fields: {

    Updated 2026-11-19T01:25:44.705Z.

  5. minimal-foundry commented on Nov 19, 2026

    @minimal-foundry
    Contributor

    That /implement is held, not dropped. The container platform had no instance to give the coder: its pool of prepared containers was full, which happens most just after a deploy. It is asked again every 10 minutes for up to 30.

    Nothing to type again: the command gets a rocket when its coder starts, or a refusal that names the reason.

    What the platform said

    could not start the coder: Error: there is no container instance that can be provided to this durable object

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

    bugSomething isn't workingkind:taskA task the plan skill rendered; the body carries ## Task

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0