Repository navigation
Improve JRuby selector compatibility - #193
samuel-williams-shopify wants to merge 4 commits into
Conversation
|
cc @headius |
Assisted-By: devx/242ffd92-f36a-421a-88b9-270e5488162a
Assisted-By: devx/242ffd92-f36a-421a-88b9-270e5488162a
Assisted-By: devx/242ffd92-f36a-421a-88b9-270e5488162a
0c16934 to
8e36b49
Compare
Assisted-By: devx/242ffd92-f36a-421a-88b9-270e5488162a
|
I'll jump in to help where I can! |
|
@headius I filed a few upstream bug reports on JRuby.
Also, what's the current state of Loom/ |
|
@ioquatix @headius I ran io-event main against current JRuby master, and most of the JRuby skips here aren't needed anymore. These pass now:
The Fixes in progress:
Still needed:
With those in, the only JRuby failure left on macOS is the "read and write from two different fibers" test. That's a kqueue selector bug in jnr-enxio (jnr/jnr-enxio#50), and the test passes on Linux. |
|
Very exciting progress! |
|
FYI the jnr-enxio fix is merged and will be released and incorporated into 10.0.8.0 and 10.1.3.0 coming this week or early next. |
Summary
IO::Bufferoperations and using nonblocking Ruby IO methods where neededSelector.nonblockrestore nonblocking state explicitly and ensure the helper is loaded for the pure Ruby selectormain, without the old fork diagnostic workflow/test commitsVerification
bundle exec rubocopbundle exec bake testNote: this replaces the old
interrupt-fixPR branch.