-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Bump tenacity to 6.2 #11313
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
Bump tenacity to 6.2 #11313
Conversation
ryw
left a comment
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.
+1
|
@kaxil -> I would like to check if this works - do not merge it please before I take a look. I have a feeling we have some problem with upgrading constraints and I would like to have closer look tomorrow on it. |
potiuk
left a comment
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.
Just want to take a look at this before it gets merged.
|
why did we limit it in the first place? something must have broken with 5.2? |
|
I think @kaxil wants to update constraints. But I am afraid it will not work this way. I will take a look at this thing tomorrow. |
|
Just to be clear, I want to update requirements not just constraints. Constraints is the by-product. I am familiar with the current CI problem regarding constraints. |
There is no reason to limit tenacity. One of my upcoming PRs (or a commit in scheduler-ha PR) will use a new feature available in the newer version.
One of the reasons for creating a separate PR for this is so that constraints are updated and when I create new PR (or merge to scheduler-ha PR) it will run against a newer version of tenacity because of the upgraded constraints, without it, it will error.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.