fix: Pin Boto3 version to avoid breaking change #247
Merged
+10
−10
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
jstlaurent
requested review from
achchala,
Andrewq11,
mercuryseries and
roselynh100
cwognum
reviewed
Jan 16, 2025
There was a problem hiding this comment.
Thanks @jstlaurent!
Could you also make the change in the env.yml file?
cwognum
approved these changes
Jan 16, 2025
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.
Changelogs
Checklist:
Add tests to cover the fixed bug(s) or the newly introduced feature(s) (if appropriate).Update the API documentation if a new function is added, or an existing one is deleted.feature,fix,chore,documentationortest(or ask a maintainer to do it for you).Fixes #246.
Boto3 has changed its default behavior in 1.36.0. The header that is now added automatically is not supported by all S3-compatible services, such as Cloudflare R2, which is the backing store for the Polaris Hub storage. The suggested configuration to disable the new behavior does not appear to fix this issue in our case. I've elected to pin the Boto3 version for now.