Closed Segaja closed 1 year ago
bump
Do you mind making a PR? Thanks!
https://github.com/socketry/nio4r/pull/239/commits/e53e5d518962686e8ca093ee814739b1fa7edf25 is the root cause for the issue. The question is if it should be reverted, or if the constant should be pre-defined outside of the block. But revert is probably easier solution.
Boy, that was stupid (I authored the commit). Don't recall. I think the intent was to not load openssl when the spec files load, so some specs may run without openssl being loaded. Maybe change
RSpec.describe OpenSSL::SSL::SSLSocket do
to
RSpec.describe 'OpenSSL::SSL::SSLSocket' do
Will this be patched in the code soon, @MSP-Greg ?
@Segaja Not sure. If the above is used, other specs can be run without loading Ruby's OpenSSL. Not sure if that's helpful.
Happy to do a PR with the above...
@MSP-Greg I can confirm the fix above with the quotes works. For now I patch it manually in the build for arch, but it would be nice if it would be fixed in the project itself.
I've fixed this by moving the require to before the describe block.
I guess the
require "openssl"
block should be outside of this block.