8000 Box CLI: exit with the reserved codes for a missing (4) or ambiguous (2) box name · Issue #2816 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

Box CLI: exit with the reserved codes for a missing (4) or ambiguous (2) box name #2816

Open

Description

@norrietaylor

Box CLI follow-up from the architecture review of #2811 (T111), condition C1. By the person's ruling of 2026-10-31, this is box CLI work, not NET.

Every min session miss exits 1 today. The reserved exit-code table (gominimal/arch, the box spec's exit codes) gives 4 for "not found" and 2 for a usage error such as an ambiguous name. T111 adds two typed refusals that the binary could map:

  • BoxNotFound: "no running VM has a box named '' …" → 4
  • AmbiguousBoxName: a name on more than one VM → 2

What to do

  • Adopt the exit-code table for min session and the box commands in failure_exit_code (crates/minimal/src/main.rs). Re-export the error types from the minimal crate so the binary can downcast them.
  • Apply the codes to every miss, not only these two, so that scripts see one rule.

Activity

  1. added
    kind:taskA task the plan skill rendered; the body carries ## Task
    on Oct 31, 2026
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

    kind: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