bobu-putheeckal opened a new pull request, #67433: URL: https://github.com/apache/airflow/pull/67433
Fix `CloudComposerExternalTaskSensor` and `CloudComposerExternalTaskTrigger` so execution-range state checks only succeed after at least one task instance is actually inside the requested open interval. Why this is needed: - the previous helper returned `True` when every returned task instance was outside `execution_range` - that allowed the sync sensor, and the deferrable trigger path using the same helper, to report success without any relevant in-window task instance - out-of-window task instances are still ignored when an in-window task instance satisfies the requested states What is covered: - all returned task instances outside the execution range - only boundary task instances, preserving the existing open-interval boundary behavior - mixed out-of-window and in-window task instances for Airflow 2 `execution_date` and Airflow 3 `logical_date` response shapes Tests: - `cd providers/google && uv sync` - `cd providers/google && uv run pytest tests/unit/google/cloud/sensors/test_cloud_composer.py::TestCloudComposerExternalTaskSensor tests/unit/google/cloud/triggers/test_cloud_composer.py::TestCloudComposerExternalTaskTrigger` (27 passed) - `cd providers/google && uv run ruff check src/airflow/providers/google/cloud/sensors/cloud_composer.py src/airflow/providers/google/cloud/triggers/cloud_composer.py tests/unit/google/cloud/sensors/test_cloud_composer.py tests/unit/google/cloud/triggers/test_cloud_composer.py` - `git diff --check` Note: a root-level `uv run pytest ...` attempt was not used for validation because it tried to build the full Airflow all-providers environment and failed on unrelated `jpype1` Java runtime discovery. The provider-scoped environment and tests above passed. closes: #67051 --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Codex (GPT-5) -- 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]
