-
-
Notifications
You must be signed in to change notification settings - Fork 183
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 botocore to 1.29.76 #999
Conversation
see work I started in #974, we need to research new codepath: SSOTokenProvider._refresher |
oh, I see something along those lines, does this PR account for that? |
This comment was marked as outdated.
This comment was marked as outdated.
I just pushed a commit that supports async token refresh. Please note that this is currently untested. Is anyone able to give it a try and/or suggest unit tests? |
aha, @jakob-keller you da man. Ok for stuff like this I typically pulled tests from botocore. You can see some of our adaptations here: https://github.com/aio-libs/aiobotocore/tree/master/tests/boto_tests. where possible keeping the tests as similar as possible |
OK, I will give it a shot. I just discovered another new blocking codepath in regions.py. Will address that, too. |
oops, forgot probably easier doing it in https://github.com/aio-libs/aiobotocore/tree/master/tests/python3.8/boto_tests, no reason to make it 3.6 compatible |
OK, I addressed the failing unit tests and the second blocking codepath. It's working locally on my machine. Could you trigger CI again, please? I haven't gotten around to adding new tests yet. Will try to do that in the coming days. |
@thehesiod Could you trigger CI again, please? I want to make sure existing tests are fine before I add anything new. Thanks! |
@jakob-keller thanks again, sorry for delay, work + fam have been non-stop. |
OK, I had a look at the unit tests from upstream and added and/or modified those that I believe are relevant. @thehesiod: Could you please run CI again to check if there are any remaining issues? |
Well it looks like test coverage is subpar. Is that a hard requirement? I am not terribly familiar with the test suits of this repo nor upstream, which makes me rather doubtful that I can contribute much more without specific guidance. Any input? Thanks! |
I think the tests may not be running because they're not marked moto: https://github.com/aio-libs/aiobotocore/blob/master/tests/test_monitor.py#L6. Right now we only run moto tests: https://github.com/aio-libs/aiobotocore/blob/master/Makefile#L25 you can run the tests locally as well to check |
I would love to see this. I'm trying to decide whether to use aioboto3 in my project and it being ~7 months behind boto3 worries me a bit. For example, if there's a critical bug fix to boto3 and it takes long for it to be picked up by aioboto3 that would be a cause for concern. I of course understand this is open source and people have limited time. Just wanted to share my thoughts of adopting this package as a potential user. |
OK, I believe it's ready for another spin. Awaiting CI run... |
Well, this time, I believe we are pretty close. Anything else I can do to move this forward? |
@thehesiod What do you think about the state of this PR? Anything else that I can contribute or need to address? |
@jakob-keller I think it's great, just need a sec to look over it |
looking now |
@@ -167,6 +171,7 @@ async def _create_client( | |||
) | |||
else: | |||
credentials = await self.get_credentials() | |||
auth_token = self.get_auth_token() |
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.
nice work piping this through!
Codecov Report
@@ Coverage Diff @@
## master #999 +/- ##
===========================================
- Coverage 86.86% 71.32% -15.55%
===========================================
Files 55 55
Lines 5391 5287 -104
===========================================
- Hits 4683 3771 -912
- Misses 708 1516 +808
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
looks great! Thanks so much for all your hard work! This was one of the more complicated merges. I'll get this out today |
we should point to this PR why bumping is not so simple :) |
ya I have limited time now with kids and start-up life, have any other volunteers for help with getting releases out sooner? This one took longer than expected due to the complications you can see from this PR. They added several new codepaths that needed to be async'ified |
I feel you!
Count me in |
Really appreciate the work here guys. Thanks so much! |
Is a release planned with this or more recent botocore dependency? s3fs is being hit by the large number of releases botocore has had since the last 2.5.0 dask/dask#10276 |
This has been released as |
Er, enough to convince conda that downgrading boto3 is preferable to downgrading s3fs by several years. |
Description of Change
The botocore dependency has not been updated in a while, causing a number of downstream issues and incompatibilities.
Assumptions
Diff between previous and new botocore sources: boto/botocore@1.27.59...1.29.76
Checklist for All Submissions
Checklist when updating botocore and/or aiohttp versions