-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Remove limits for aiobotocore limiting boto3 #50285
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
Conversation
Those limits are causing pip to not install latest amazon provider when upgrading to latest versions in general.
|
I think I found out why in latest RC image of Airflow, we do not get latest amazon provider installed. |
|
Reopened to rebuild it with all tests |
o-nikolas
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.
lgtm if tests build/pass as expected.
aritra24
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.
Thanks for the explanation Jarek.
|
All checks passed :) .. so merging. |
Those limits are causing pip to not install latest amazon provider when upgrading to latest versions in general.
Those limits are causing pip to not install latest amazon provider when upgrading to latest versions in general.
^ 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 airflow-core/newsfragments.