github-actions[bot] opened a new pull request, #74969: URL: https://github.com/apache/airflow/pull/74969
Four CLI paths build a DagBag straight from bundle.path without first calling bundle.initialize(). A LocalDagBundle already has its files on disk, so the gap is invisible in local development and in the test suite; a bundle that materialises its files in initialize() - a Git bundle clones the repo there - is still an empty path at that point. dags list and dags list-import-errors then report an empty bundle and no import errors and exit 0, so a CI gate built on them passes while the Dag files are never read. tasks test, dags test and the --dag-regex lookups fall through to the "search every configured bundle" path, which re-fetches and syncs every bundle to the metadata DB and can return a same-named Dag from a bundle other than the requested one. The three call sites that already initialize - dags report, dags reserialize and the fallback loop in get_bagged_dag - show the intended shape; that fallback loop got its call in #53699, which fixed only the one occurrence it was reported for. (cherry picked from commit 62641fa9ac01cf2443936790fdd1265ebfd57b86) Co-authored-by: Y-C <[email protected]> Co-authored-by: Eason09053360 <[email protected]> -- 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]
