The GitHub Actions job "Tests (AMD)" on airflow.git/feature/coordinator/dag-bundle-name has succeeded. Run started by GitHub user jason810496 (triggered by jason810496).
Head commit for run: ae81e0d6ea8beaf8ba7bce24e6dd0e4c2821b0a2 / LIU ZHE YOU <[email protected]> Resolve coordinator Dag bundles without importing the task runner A language-SDK task start needs a bundle materialized on disk before the subprocess can be launched, but reaching that through the task runner made every such start pay for the operator tree, pydantic, and OTel plumbing that the supervisor side never uses. The bundle lifecycle now lives on its own, so the coordinator depends on the Dag-bundle machinery alone. The bundle-name check a coordinator runs at construction and the class-importing parse the manager runs at startup previously read the configuration independently, so the two could disagree about what is configured. Keying the parsed configuration on the configuration itself lets both share one snapshot while a configuration change is still picked up. Subclasses had to declare the name of their explicit-root kwarg separately from its value, which is two things to keep in step for one piece of information. Report URL: https://github.com/apache/airflow/actions/runs/31348688874 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
