shivaam commented on PR #71589: URL: https://github.com/apache/airflow/pull/71589#issuecomment-5381182844
Yes, broadly. `generated/known_clear_db_setup.txt` is the migration list for the patterns this guard detects. It contains one entry per affected file, not per cleanup call. Follow-up PRs can take small groups from that list, fix cleanup in the fixture or test that owns the rows, and remove the setup-time `clear_db_*` calls. Once a file has no remaining detected calls, regenerating the list removes it, and the guard prevents it from being added back. We’re also experimenting separately with a runtime detector and the `dag_maker` asset cleanup gap. Those may help prioritize later work, but they aren’t part of this PR or committed next steps yet. -- 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]
