mik-laj opened a new pull request #11960: URL: https://github.com/apache/airflow/pull/11960
Part of: https://github.com/apache/airflow/issues/11925 I added support for catching a few additional kinds of problems that can happen while loading DAGs. In particular: - deprecation warnings - database queries New warnings are only displayed in a separate list view. And on the main screen, only critical errors are still displayed, which prevent the DAGs from loading correctly. It's still a POC and I have a lot of work to do on it, but I would like to ask what do you think? Previously, there were requests to make saving these messages optional, but I'm not sure if this is necessary if these errors are only visible on a separate screen. This shouldn't cause performance issues or anything else, so the extra option would be redundant. It just serves to hide the problems from management. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.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. For queries about this service, please contact Infrastructure at: [email protected]
