-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bring back SHUTDOWN-related constants #34063
Conversation
Pending test fixes |
ed5a9fc
to
fce7f86
Compare
82eb4df
to
64059a8
Compare
This should restore code compatibility to 2.6 and prior. Note that the constants would not appear in documentation since they are deprecated and not use in Airflow core anyway anymore.
64059a8
to
31f65d1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The failing test is a known flaky test so re-run or merge with main might fix it
BTW. I think I fixed the flaky test in #34075 so likely rebasing it woudl be flaky-free, but I re-run those failing tests now. |
This should restore code compatibility to 2.6 and prior. Note that the constants would not appear in documentation since they are deprecated and not use in Airflow core anyway anymore. (cherry picked from commit 1ae2976)
This should restore code compatibility to 2.6 and prior. Note that the constants would not appear in documentation since they are deprecated and not use in Airflow core anyway anymore.
See discussion around #33746 (comment)
The value on
JobState
was not brought back since that particular enum was only added in 2.7 and should not technically cause any compatibility issues. I also added some additional docstrings so those constants would not appear in documentation added in #34059. Those who already know about the values can continue to use them, but this should reduce additional usages.