I am seeing exception messages expanded to: X509_STORE_add_cert: cert already in hash table while the test is for exactly cert already in hash table as seen here:
|
raise e unless e.message == 'cert already in hash table' |
Not sure when the error message changed but should we have a more lenient test of: e.message =~ /cert already in hash table/ ?
Without it it fails to connect due to a raised exception.
System: Amazon Linux 2, ruby 3.3.2
I am seeing exception messages expanded to:
X509_STORE_add_cert: cert already in hash tablewhile the test is for exactlycert already in hash tableas seen here:em-http-request/lib/em-http/http_connection.rb
Line 56 in 91cee59
Not sure when the error message changed but should we have a more lenient test of:
e.message =~ /cert already in hash table/?Without it it fails to connect due to a raised exception.
System: Amazon Linux 2, ruby 3.3.2