kaxil opened a new pull request, #73959: URL: https://github.com/apache/airflow/pull/73959
A short-circuit task inside a mapped task group stopped skipping the task after it in 3.2.0. Each map index of a task in a mapped task group runs as its own task instance, so `SkipMixin` writes the skip decision to XCom under that map index. #62287 changed `NotPreviouslySkippedDep` to read that XCom at `map_index=-1` unless the parent is a `MappedOperator`, to fix an unmapped `LatestOnlyOperator` upstream of a mapped task. A task inside a mapped task group is a plain operator whose `is_mapped` is False, so the dep read `-1`, found no decision, and let the downstream task run. The dep now checks `get_needs_expansion()`, which is true for a mapped operator and for any task inside a mapped task group: the tasks that write XCom per map index. An unmapped parent still reads `-1`, and the regression test from #62287 passes unchanged. A gate that returns False for odd map indexes, `gate(v) >> printstr(v)` inside a task group expanded over `[0, 1, 2, 3]`, run by the scheduler before and after the change:   related: #55225 --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- 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]
