shahar1 opened a new pull request, #76172: URL: https://github.com/apache/airflow/pull/76172
Manual backport of #76133 to `airflow-ctl/v0-1-test` for 0.1.6. The automatic backport (run 41203511872) stopped on a conflict in `airflow-ctl/tests/airflow_ctl/ctl/commands/test_dag_command.py` and opened nothing. `airflowctl dags pause|unpause` printed `Dag <operation> successful <dag_id>` and `Further Dag details:` to stdout ahead of the `--output` data, so `airflowctl dags pause my_dag -o json | jq .` failed: stdout was not valid JSON. The error message on failure went to stdout as well. These lines now go to stderr, as on `main`; stdout carries only the requested output format. In a terminal the visible output does not change; scripts that captured stdout for these status lines will now find them on stderr (exit code unchanged), which may deserve a line in the 0.1.6 release notes. Resolution: the source change is identical to `main` (the `+`/`-` lines of `dag_command.py` match). This branch has no `dags drain`, so the conflict was only in the test file: the two new tests are kept for `pause`/`unpause`, the `drain` rows of their parametrize lists and the `main`-only drain tests in the surrounding context were not brought over, and `import json` was added. Original author kept. Tested on the branch: `uv run --project airflow-ctl pytest airflow-ctl/tests`: 607 passed; the four new test cases fail without the source change. The `airflow-ctl-tests` integration runner merges stderr into stdout, so the `dags pause/unpause example_bash_operator` integration commands are unaffected. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Fable 5.1, with Sonnet 5.5 and Opus 5.5 subagents) Generated-by: Claude Code (Fable 5.1) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
