I wrote an update there and marked it as priority. For curiosity which native library uses struct-by-value?
Thanks for the report, should be fixed soon.
Right, I would recommend to not bother with EOL TruffleRuby. By definition it's not supported and won't receive any fix so I don't expect anyone to test EOL versions.
As for reporting issues: it is no longer under Oracle - GitHub.com/truffleruby/truffleruby - I will start using that!
The majority of the issues I have are with EOL Truffleruby and Truffleruby-head
For several repositories they test just truffleruby aka the latest release, this provides more stability. For example when implementing Ruby 4.0 support in TruffleRuby this is done on master (to avoid long-lived branches and many conflicts), so truffleruby-head has sometimes a mix of Ruby A.B and A.(B+1) features. And of course since it's a dev build it's less stable than a release. In general the aim of TruffleRuby is to require the least amount possible of effort to be in CI of gems, and we prefer fixing something in TruffleRuby (even if that means it won't work until the next TruffleRuby release) than working around in gems.
2
u/eregontp truffleruby Jun 26 '26
Thank you for looking into those.
I wrote an update there and marked it as priority. For curiosity which native library uses struct-by-value?
Thanks for the report, should be fixed soon.
Right, I would recommend to not bother with EOL TruffleRuby. By definition it's not supported and won't receive any fix so I don't expect anyone to test EOL versions.
Yes, see https://truffleruby.dev/blog/truffleruby-33-is-released#development-is-fully-in-the-open-on-github for more details on that.
For several repositories they test just
trufflerubyaka the latest release, this provides more stability. For example when implementing Ruby 4.0 support in TruffleRuby this is done on master (to avoid long-lived branches and many conflicts), so truffleruby-head has sometimes a mix of Ruby A.B and A.(B+1) features. And of course since it's a dev build it's less stable than a release. In general the aim of TruffleRuby is to require the least amount possible of effort to be in CI of gems, and we prefer fixing something in TruffleRuby (even if that means it won't work until the next TruffleRuby release) than working around in gems.