Arunodoy18 commented on PR #60761: URL: https://github.com/apache/airflow/pull/60761#issuecomment-3768484775
Yes — I reproduced the behavior locally while validating the fix. Although the original report referenced Airflow 2.x, the same silent DAG override still occurs in Airflow 3.x because the DagBag loading logic remains unchanged: when multiple DAG files define the same dag_id, the later parsed DAG replaces the previous one without any visibility. I verified this by: - Running Airflow 3.x locally - Creating two DAG files with identical dag_id but different task graphs - Observing that only one DAG remains active depending on parse order, with no warning This confirms the issue is still present in 3.x and the warning-based safeguard introduced in this PR applies correctly to both 2.x and 3.x behavior. -- 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]
