You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jobs@airflow.apache.org by GitBox <gi...@apache.org> on 2026/08/17 09:49:06 UTC

[GH] (airflow/zip-dag-subfolder-discovery): Workflow run "Tests (AMD)" is working again!

The GitHub Actions job "Tests (AMD)" on airflow.git/zip-dag-subfolder-discovery has succeeded.
Run started by GitHub user piotrlinski (triggered by piotrlinski).

Head commit for run:
612339a1dde3c6ced2ca0e5e3010d9bd886fccfe / piotrlinski <pi...@gmail.com>
Discover Dags in sub-folders of packaged (zip) Dag bundles

Only .py/.pyc files at the root of a zip archive were imported; a Dag file
placed in a sub-folder was silently skipped, giving no clue why it never
appeared. Zip archives are a supported way to ship a Dag together with its
vendored packages, and organising Dags into sub-packages inside the archive
is a natural layout that previously did not work.

A member in a sub-folder is now imported when that folder — and every folder
above it — is an importable package (contains an __init__.py), which is what
zipimport requires to reach it. Parent packages are imported before their
sub-modules so autoregistered Dags are attributed to the right module, and
stale modules the archive owns are evicted from sys.modules first so members
resolve against this archive. A Dag file in a non-package folder cannot be
imported from a zip, so instead of being dropped silently it is skipped and a
warning names the unreachable file and how to fix it.

Report URL: https://github.com/apache/airflow/actions/runs/32011598767

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: jobs-unsubscribe@airflow.apache.org
For additional commands, e-mail: jobs-help@airflow.apache.org