Eason09053360 opened a new pull request, #71500: URL: https://github.com/apache/airflow/pull/71500
`DBDagBag.iter_all_latest_version_dags()` promises the latest version, but the query returned every `serialized_dag` row, so a Dag was walked once per version it had. Its one production caller is the FAB auth manager's Dag permission sync, which therefore re-synced the same dag_id once per version. Same origin and same fix as #70934: reuse the select that picks the highest `version_number` per dag_id. That select is now used from a second module, so it loses its leading underscore. `SerializedDagModel.read_all_dags()` is not used here on purpose — it materialises every Dag into a dict and ignores `load_op_links`, while this method is deliberately a non-caching generator. related: #70934 --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 5) Generated-by: Claude Code (Opus 5) 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]
