Avoid autoloading openssl
to try help with jruby load service issues
#3809
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.
What was the end-user or developer problem that led to this PR?
We got a CI failure on jruby with the following error:
It's here: https://github.com/rubygems/rubygems/runs/857727761.
What is your fix for the problem, implemented in this PR?
This most likely points to the same jruby issues we've been workarounding lately where jruby crashes with a missing constant error when you require and set an autoload for the same thing.
So, add the same workaround as in other related tickets and don't autoload
openssl
.This is code inside
net-http-persistent
, so adding a note too about why we're doing this.This is a follow up to #3751, #3770, #3771, and #3781.
Tasks:
I will abide by the code of conduct.