Update S3 plugin in containers to fix segfault #1207
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
jhiemstrawisc
added
bug
|
@jhiemstrawisc For the patch to 7.7, how do we want to do it? There's no source code change and it will only affect containers. Do we want to only release a container build with a release note (but without the actual git tag)? |
turetske
approved these changes
May 1, 2024
|
I think your approach is reasonable. Can we rebuild containers based on this PR for the previous v7.7.X releases without creating a new tag? |
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.
The
v0.1.1plugin had a snippet of code that wasn't thread safe, but was only triggered in the case of PUTs. That has been fixed/tagged upstream in this issue.This PR updates the plugin version used in our containers.
@haoming29, when this is merged we should also patch it into 7.7