-
-
Notifications
You must be signed in to change notification settings - Fork 123
Support jruby #516
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
I look forward to playing with benchmarks and seeing how we can make the JRuby support superfast! |
Things we need to do to make this happen:
|
FFI? There's at least one known JRuby issue with FFI callbacks on Apple Silicon that requires some low-level C work (probably by me 😭). |
@headius, the thing is, other callbacks work as expected, so I think it's rather a misuse/misconfiguration. I'll get back to you next week when I look into this with more info. |
Revisiting this because it came up today... Still crashes on my M1 MBA during specs:
Weirdly enough, if I force JIT in JRuby, it does not crash. There are some peculiar warnings, though:
Final result of this forced-JIT run:
Not bad (and obviously fork specs should just be skipped), but we obviously need to figure out that crash. |
Yeah I do recall this crash on oauth. WHen you disable oauth bearer, is the rest of the specs working as expected? |
Btw @headius we can work on this somewhere around RubyKaigi if you fancy. |
I can reproduce:
|
|
@headius you know when actions will get 10.0.0.0? ref https://github.com/karafka/rdkafka-ruby/actions/runs/14488191323/job/40638287789?pr=571 |
I run tests on most recent jruby stable and FFI aside from one case (fixable) works ok. We could rollout the jruby support easily.
The text was updated successfully, but these errors were encountered: