thesuperzapper opened a new issue, #24060: URL: https://github.com/apache/airflow/issues/24060
### Apache Airflow version 2.3.1 (latest released) ### What happened As of Airflow 2.3.0 the `airflow db check-migrations -t 0` command will ALWAYS think there are unapplied migrations (even if there are none to apply), whereas, in Airflow 2.2.5, a single check would be run succeessfully. This was caused by PR https://github.com/apache/airflow/pull/18439, which updated the loop from [`while True`](https://github.com/apache/airflow/blob/2.2.5/airflow/utils/db.py#L638) (which always loops at least once) to [`for ticker in range(timeout)`](https://github.com/apache/airflow/blob/2.3.0/airflow/utils/db.py#L696) (which will NOT loop if timeout=0). ### What you think should happen instead _No response_ ### How to reproduce _No response_ ### Operating System All ### Versions of Apache Airflow Providers _No response_ ### Deployment Other ### Deployment details _No response_ ### Anything else _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
