vincbeck opened a new pull request, #68634:
URL: https://github.com/apache/airflow/pull/68634

   ## Summary
   
   When `multi_team` is enabled, tasks remain in "No status" indefinitely and 
Dag runs never complete.
   
   The root cause is that `get_running_dag_runs_to_examine()` returns a 
`ScalarResult` (a one-pass SQLAlchemy iterator). The multi-team code path added 
in #68108 iterates it to build a team-name mapping, exhausting the iterator 
before `_schedule_all_dag_runs` can consume it. As a result, zero Dag runs get 
processed and no task instances ever transition out of None state.
   
   The fix materializes the `ScalarResult` into a `list()` so it can be safely 
iterated multiple times.
   
   <!--
   Generated-by: [Tool Name] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * 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]

Reply via email to