mef commented on issue #73678: URL: https://github.com/apache/airflow/issues/73678#issuecomment-6263248241
Hi, I'd like to raise a potential issue with the solution of rejecting Cyclic TaskGroup dependencies break at parse time. Here's our situation to describe the potential issue: One DAG containing a cyclic task group dependencies runs daily in production, and since Airflow v3.3.1, the grid view does not show the groups and tasks data anymore - as per the issue reported here. We fixed it by reorganizing the groups so that there are no more cycles at group level, 6 days ago. When limiting UI display to only 'last 5 runs' - so only the new grouping is in place, then the groups show up correctly in the UI: <img width="1287" height="489" alt="Image" src="https://github.com/user-attachments/assets/1faa9de9-c38f-4449-b61a-69bc2608adc8"; /> However, when loading the page with the default display of 'last 10 runs', the older versions of the DAG with previous grouping setup is parsed, and we end up with the current issue again of groups and tasks not showing up. <img width="1287" height="489" alt="Image" src="https://github.com/user-attachments/assets/2dc6d060-6f62-4d79-a239-35c16611f597"; /> So whenever rejecting DAGs with 'cyclic taskgroup dependencies', how would older versions be handled? Will users be able to deploy corrected DAGs, without risking rejections because older versions have the issue? Thanks. -- 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]
