-
Notifications
You must be signed in to change notification settings - Fork 191
TypeError
on require 'digest/sha2'
#2511
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
TypeError
on `require 'digest/sha2'TypeError
on require 'digest/sha2'
I cannot reproduce, could you share your
|
The full backtrace you get without the |
hmm, right, it happens only inside |
ah, quite easy, require 'bundler/inline'
gemfile do
source 'https://rubygems.org'
gem 'digest', '3.0.0'
end
require 'digest/sha2' |
I guess could be #1390 duplicate? |
Sorry, I missed your reply somehow. That repro works correctly now (no output and no error), because TruffleRuby master already ships with digest 3.0.0 as a default gem.
In general it's probably better to avoid an explicit dependency on the digest gem, but I guess maybe it's through a transitive dependency or so? We'll likely need fixes in https://github.com/ruby/digest to make this work (either always use the builtin version, or make sure the C extension works and add truffleruby in CI there). |
After setting
|
Yep, it's transitive via updated net-smtp that we need for ruby/net-smtp#26. So I guess it's a minor incompatibility issue with particular cext at the end of the day? If it would work — even better, anyway. |
Yeah, that's a fair assessment, it was a bug of Regarding the issue label/changelog, compatibility is typically used for "didn't work yet" and bug for incorrect behavior which can cause incorrect result. |
To clarify, it'll be fixed soon and it will be in the next release. |
* Needed by the digest gem: #2511 (comment)
Also ran into this issue after I had to add
Should I wait for the next TruffleRuby release or is there a workaround to ignore the |
truffleruby-dev has this My understanding is those gems should be under FWIW, there is also |
The text was updated successfully, but these errors were encountered: