potiuk commented on PR #39908:
URL: https://github.com/apache/airflow/pull/39908#issuecomment-2208937176
Hmm.. seing it - I am not sure if warning is a good idea. The thing with
warnings is that you should have an "easy" way to get rid of the warning - and
changing your dashboard/metrics is likely not an easy task - and I think one of
the worst cases with warnings is to not allow people to silence them easily (by
fixing them) . I am just thiking whether we should allow a third state of the
switch ("legacy" ?) to allow the users to deliberately set it and silence the
warning ?
BTW. The way how to treat warnings in tests is described in the docs:
https://github.com/apache/airflow/blob/main/contributing-docs/testing/unit_tests.rst#handling-warnings
--
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]
