shahar1 opened a new pull request, #76118: URL: https://github.com/apache/airflow/pull/76118
Partial backport of #68028 to `airflow-ctl/v0-1-test`, following the precedent of #76076 (`DagRunType` for #63733): only the enum value and what is generated from it are backported, not the Human-in-the-loop feature itself. airflowctl 0.1.x is generated from the 3.2.1 API spec, so its `TaskInstanceState` has no `awaiting_input`. Against an Airflow 3.3+ API server, `taskinstances list` and `tasks states-for-dag-run` crash with a pydantic `ValidationError` as soon as a Dag run contains a HITL task waiting for input. Adding the member lets 0.1.6 read those task instances from 3.3.x and 3.4.x servers while still working against 3.2.x (the value is never sent by older servers). As in #76076, the core enum (`airflow-core/src/airflow/utils/state.py`), both OpenAPI yamls, the generated UI types and the task-sdk mirror are updated so `airflow-ctl/src/airflowctl/api/datamodels/generated.py` stays regenerable from this branch; the upstream `State` helper sets are intentionally not extended here (same choice as #76076). Tested: - `breeze testing airflow-ctl-tests`: 562 passed (new test: `test_task_instance_state_accepts_awaiting_input`, which fails without the change). - Live, against real `apache/airflow:3.3.2-python3.12` and `3.4.0rc1-python3.12` servers with a HITL task parked in `awaiting_input`: `taskinstances list` and `tasks states-for-dag-run` return the state instead of a traceback; against `3.2.2-python3.12` behaviour is unchanged. - `breeze testing airflow-ctl-integration-tests` against 3.2.2, 3.3.2 and 3.4.0rc1 with the three 0.1.6 fixes combined: identical results to the unpatched branch (the suite has no HITL case). --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Fable 5.1) 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]
