leossantos opened a new pull request, #64322: URL: https://github.com/apache/airflow/pull/64322
Port to **main** (Airflow 3) of the scheduler guard from [#63546](https://github.com/apache/airflow/pull/63546): `DagModel.dags_needing_dagruns` could treat asset-triggered DAGs as ready for a new run when they had `AssetDagRunQueue` rows but **no** `SerializedDagModel` in the same evaluation window. The asset timetable / condition path was not applied consistently for those DAGs, which could allow premature asset-triggered DagRuns while the DAG processor was mid–parse cycle. This change removes such `dag_id`s from the in-memory `adrq_by_dag` / `dag_statuses` maps until serialization exists. **`AssetDagRunQueue` rows are not deleted**; the scheduler can re-evaluate on a later run. A **DEBUG** log records skipped DAGs (missing serialization). The `dags_needing_dagruns` docstring documents this behavior. **Tests:** two `TestDagModel` cases cover missing `SerializedDagModel` (single and multiple DAGs), DEBUG log expectations, sorted `dag_id` list in the message, and **assert `asset_dag_run_queue` row counts unchanged** after `dags_needing_dagruns`. related: [#63546](https://github.com/apache/airflow/pull/63546) --- ##### Was generative AI tooling used to co-author this PR? - [x] Yes (please specify the tool below) <!-- Generated-by: [Cursor] 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]
