The GitHub Actions job "Tests (AMD)" on airflow.git/backport-038ece6-v3-3-test has succeeded. Run started by GitHub user github-actions[bot] (triggered by eladkal).
Head commit for run: 012ca5fedcbf739c11737a00ce898c62843cf234 / Sebastián Ortega <[email protected]> [v3-3-test] Don't deactivate DAG bundles owned by other dag-processors (#69964) `DagBundlesManager.sync_bundles_to_db()` marks every stored bundle that is not in the calling process's config as inactive. This assumes the caller sees the complete bundle configuration. When multiple dag-processors are each configured with a partial config (one bundle per processor, a natural way to shard parsing), each processor treats the other processors' bundles as "no longer found in config" and disables them. Processor A disables B's bundle, B disables A's, and they flip `dag_bundle.active` on every parse cycle -- the deployment never converges and continuously logs "DAG bundle ... is no longer found in config and has been disabled" for bundles that are actively configured elsewhere. Add a `deactivate_missing` flag (default `True`, preserving existing single-processor behavior) and have `DagFileProcessorManager.sync_bundles()` pass `deactivate_missing=False` when the processor was started with a bundle filter (`--bundle-name` / `bundle_names_to_parse`), i.e. when it only owns a subset of the bundles. closes: #69963 related: #69698 (cherry picked from commit 038ece6acf12794b2ae8ec84349a31e9cb629a4c) Co-authored-by: Sebastián Ortega <[email protected]> Generated-by: Claude Code following the guidelines Report URL: https://github.com/apache/airflow/actions/runs/29582544649 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
