Arunodoy18 commented on issue #60559: URL: https://github.com/apache/airflow/issues/60559#issuecomment-3765846429
Thanks for reporting this — this is indeed risky behavior, especially given the nondeterministic DAG parse order. For an initial fix, I’d like to start with a minimal and backward-compatible safeguard in the scheduler’s DAG parsing layer: • Detect when a DAG with an already-seen dag_id is being added to the DagBag • Log a clear warning including the dag_id and both conflicting file locations • Keep existing behavior unchanged (no failure or UI changes in this first step) This mirrors how Airflow handles duplicate task IDs (warn first), and should provide visibility without introducing breaking changes. If this sounds good, I can prepare a small PR focused only on duplicate detection + warning. -- 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]
