Use thread-safe digest creation mechanism#483
Merged
mhenrixon merged 1 commit intomhenrixon:masterfrom Mar 30, 2020
Merged
Conversation
… module is not thread-safe
Owner
|
Wow 😮... Who would have thunk? Cheers for the contribution. I will get it merged and back-ported sometime today. |
Owner
|
Released as |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
We've been getting the following error intermittently (like once a month):
Digest::Base cannot be directly inherited in RubyIt turns out that the Digest::MD5 module used for creating the unique digest for the jobs is not thread-safe. Apparently many people have been having this issue for a long time (e.g. see aws/aws-sdk-ruby#525). Using the OpenSSL module instead is reported to have solved the problem.