kevinveenbirkenbachandClaude Opus 5 cc76272217 fix(test-e2e-cli): fail the CLI test on a test.env line that fails ...

run_one.yml sourced the rendered env with `set -a && . test.env && set +a`.
Nothing aborted on a failing line, and `.` returned only the status of the
file's last line, so a broken assignment in the middle printed a bash error
to stderr and the test ran on with the variable unset. That is how
`ONION_PORTS=25 80 ...` left the svc-net-tor port probe checking nothing.

Source it as a standalone command under `set -e`. bash ignores errexit inside
a file sourced as part of an && list, so `set -ea && . test.env` would not
help; a unit test runs the real command from run_one.yml and fails on both
the old form and that one.

The env-file quoting lint told authors that spaces are fine unquoted. For a
bash-sourced CLI test.env they are not; its message now points to
dotenv_quote instead.

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

2026-09-22 17:06:05 +02:00

..

files

test(mcp): fail the contract on a JSON-RPC error inside an HTTP 200

2026-09-10 12:47:15 +02:00

filter_plugins

…

__init__.py

…

test_run_one_env_sourcing.py

fix(test-e2e-cli): fail the CLI test on a test.env line that fails

2026-09-22 17:06:05 +02:00