Files
HAL9000 417f492e8d
CI / lint (pull_request) Successful in 1m16s
CI / quality (pull_request) Successful in 1m25s
CI / benchmark-publish (pull_request) Has been skipped
CI / typecheck (pull_request) Successful in 2m4s
CI / security (pull_request) Successful in 2m8s
CI / build (pull_request) Successful in 49s
CI / push-validation (pull_request) Successful in 48s
CI / helm (pull_request) Successful in 1m0s
CI / integration_tests (pull_request) Successful in 4m36s
CI / e2e_tests (pull_request) Successful in 4m47s
CI / unit_tests (pull_request) Failing after 9m24s
CI / docker (pull_request) Has been skipped
CI / coverage (pull_request) Successful in 23m51s
CI / status-check (pull_request) Failing after 4s
fix(cli/actor): catch typer.Exit alongside click.exceptions.Exit in run commands
Typer 0.26.7 ships its own typer._click.exceptions.Exit(RuntimeError)
which is separate from click.exceptions.Exit(BaseException). The existing
`except click.exceptions.Exit: raise` handler in actor.py and actor_run.py
did not catch typer.Exit, causing it to fall through to the broad
`except Exception` handler and exit with code 3 instead of 2.

Fix: change to `except (click.exceptions.Exit, typer.Exit): raise` in both
run() commands so typer.Exit propagates correctly through the try block.

Also update the BDD step definitions for actor_run_signature tests to add
typer.Exit to their except clauses. The steps used `except (SystemExit,
click.exceptions.Exit)` which also did not catch typer.Exit, causing those
scenarios to error rather than capture the exit code.

ISSUES CLOSED: #10461
2026-06-07 02:04:27 -04:00
..