Skip to content

fix: include command name and args in process spawn error messages#965

Merged
thesayyn merged 2 commits intoaspect-build:mainfrom
sallustfire:fix/process-spawn-error-context
Mar 15, 2026
Merged

fix: include command name and args in process spawn error messages#965
thesayyn merged 2 commits intoaspect-build:mainfrom
sallustfire:fix/process-spawn-error-context

Conversation

@sallustfire
Copy link
Contributor

Previously, spawn/status failures only showed the bare OS error (e.g. "No such file or directory (os error 2)") with no indication of what command was being invoked. Now errors include the full command and args via Debug output from std::process::Command.

This was relatively straight-forward to address with axl command spawn/status calls, but bazel spawns are less modular. There's a whole class of error there that isn't currently surfaced to users at all and might benefit from some light abstraction around sourcing bazel and the workspace. For instance, I had a developer that used a shell alias for bazel which isn't provided to the subprocess. OS error 2 was the only indication of the failure. aspect-cli also doesn't work when run via multitool because finding the bazel server gets confused by being inside the runfiles tree. This is out of scope for this fix, but figured I'd mention it in case these changes would considered beneficial.

Affected code paths:

  • ctx.std.process.command().spawn() / .status() (axl stdlib)
  • ctx.bazel.build() (bazel build/test spawn)
  • Build::server_info() (bazel info spawn)
  • Query::query() (bazel query spawn)

Changes are visible to end-users: yes

  • Searched for relevant documentation and updated as needed: no
  • Breaking change (forces users to change their own code or config): no
  • Suggested release notes appear below: yes

Error messages from failed process spawns now include the command name and arguments, making it easier to diagnose issues like missing binaries or incorrect paths.

Test plan

  • New test cases added
    • spawn_error_includes_command_and_args
    • status_error_includes_command_and_args

Previously, spawn/status failures only showed the bare OS error (e.g.
"No such file or directory (os error 2)") with no indication of what
command was being invoked. Now errors include the full command via
Debug output from std::process::Command.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 990454f64c

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Uses get_program()/get_args() rather than Debug formatting on
std::process::Command to avoid leaking environment variables.
@thesayyn thesayyn merged commit 8f93f2b into aspect-build:main Mar 15, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants