Upgrade dependencies in order to avoid backtracking #27531
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
potiuk
force-pushed
the
add-missing-version-specification-for-fab-oauth
branch
2 times, most recently
from
669823f
to
a46d55e
Compare
potiuk
force-pushed
the
add-missing-version-specification-for-fab-oauth
branch
from
a46d55e
to
63f7c0e
Compare
eladkal
approved these changes
Nov 6, 2022
|
I am afraid it will take a while to iterate on it to get it working :) |
Seems that the new `pip` have become a little more relaxed when it comes to looking for dependencies, and we need to make sure that version constraint is specified in every extra otherwise it might have hard time finding the right set of dependencies while running "eager upgrade". Over the last few days all our main builds failed because of that as pip was backtracking when performing eager upgrade.. This PR updates various dependencies to get rid of the backtracking, following the process described in the https://github.com/apache/airflow/blob/main/dev/TRACKING_BACKTRACKING_ISSUES.md
potiuk
force-pushed
the
add-missing-version-specification-for-fab-oauth
branch
from
63f7c0e
to
dde3bf8
Compare
potiuk
changed the title
|
Seems I got it back under control. Updating some of the "min" requirements - for google, amazon, authentication, flake (all those were being backtracked) - and |
|
All Right. All looks good. merging to get the main green again. |
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Nov 7, 2022
When generating constraints for released providers we hit the same `pip` resolver backtracking issue - where it took very, very long time to resolve the dependencies for installing released providers on latest airflow from sources. In apache#27531 we've added limits to provider.yaml but currently released providers do not have those limits, so until we release them, we should add the limits to "eager upgrade dependencies" in our CI image - to help `pip` to figure out the right set of dependencies much faster. Also fixed a problem with extra "." in adal specification (seems it's been ignored by `pip` anyway)
potiuk
added a commit
that referenced
this pull request
Nov 7, 2022
…27535) When generating constraints for released providers we hit the same `pip` resolver backtracking issue - where it took very, very long time to resolve the dependencies for installing released providers on latest airflow from sources. In #27531 we've added limits to provider.yaml but currently released providers do not have those limits, so until we release them, we should add the limits to "eager upgrade dependencies" in our CI image - to help `pip` to figure out the right set of dependencies much faster. Also fixed a problem with extra "." in adal specification (seems it's been ignored by `pip` anyway)
ephraimbuddy
added
the
type:misc/internal
ephraimbuddy
pushed a commit
that referenced
this pull request
Nov 11, 2022
…27535) When generating constraints for released providers we hit the same `pip` resolver backtracking issue - where it took very, very long time to resolve the dependencies for installing released providers on latest airflow from sources. In #27531 we've added limits to provider.yaml but currently released providers do not have those limits, so until we release them, we should add the limits to "eager upgrade dependencies" in our CI image - to help `pip` to figure out the right set of dependencies much faster. Also fixed a problem with extra "." in adal specification (seems it's been ignored by `pip` anyway) (cherry picked from commit a50195d)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Seems that the new
piphave become a little more relaxed when itcomes to looking for dependencies, and we need to make sure that
version constraint is specified in every extra otherwise it might
have hard time finding the right set of dependencies while
running "eager upgrade".
Over the last few days all our main builds failed because of that as pip
was backtracking when performing eager upgrade..
This PR updates various dependencies to get rid of the backtracking,
following the process described in the
https://github.com/apache/airflow/blob/main/dev/TRACKING_BACKTRACKING_ISSUES.md
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.