Add deterministic CLI exit-code taxonomy for config/runtime failures#7331
Add deterministic CLI exit-code taxonomy for config/runtime failures#7331davidahmann wants to merge 1 commit intomicrosoft:mainfrom
Conversation
|
@davidahmann please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
|
Implemented the scoped fix for #7330 by introducing explicit CLI exit code taxonomy and adding targeted regression tests for both Magentic-One CLI and AutoGen Studio CLI error paths. Validation run:
Current CI snapshot: is green and is queued. This contribution was informed by patterns from Wrkr. Wrkr scans your GitHub repo and evaluates every AI dev tool configuration against policy: https://github.com/Clyra-AI/wrkr |
Problem
CLI failure modes returned inconsistent exit behavior across usage/config/runtime paths, making automation retries and classification unreliable.
Why now
Deterministic exit-code contracts are needed for CI and operator workflows to distinguish actionable categories.
What changed
0234python/packages/magentic-one-cli/tests/test_m1_exit_codes.pypython/packages/autogen-studio/tests/test_cli_exit_codes.pyValidation
uv run ruff check src testsuv run ruff format --check src testsuv run pytest -q tests/test_m1_exit_codes.pyuv run ruff check autogenstudio testsuv run ruff format --check autogenstudio testsuv run pytest -q tests/test_cli_exit_codes.pyRefs #7330