Closed ioquatix closed 4 years ago
Could you open an issue on https://github.com/oracle/truffleruby/issues ? That's the easiest way for the TruffleRuby team to track it.
It looks like https://github.com/oracle/truffleruby/issues is getting stuck on
OpenSSL::SSL::SSLSocket behaves like an NIO selectable
.
I think pinging @oracle/truffleruby should work now as well. It's still easier to have an issue in our repo to keep track of opened issues though.
Unfortunately, that doesn't work due to what seems to be a GitHub restriction.
Note: It is not possible to @mention teams in a different organization.
I've added support for truffleruby in travis here 633a1422609422921429d9546428c1aab5b2bb27
I've added a separate build using NIO4R_PURE
so we can track these independently.
@eregon any chance of making progress on this issue?
It won't even build at the moment: https://travis-ci.org/socketry/nio4r/jobs/477209885
@ioquatix That seems caused by the gem update --system
in the .travis.yml
added in https://github.com/socketry/nio4r/commit/7d923ff0b4959467f21da9914a16188c05c3ee6f. I wouldn't recommend running that in CI, the bundled RubyGems is likely to work better than an arbitrary new version.
I've had issues when I didn't do it... let me check if it's still a problem.
Okay I removed those lines, now getting hung up in OpenSSL specs.
OpenSSL::SSL::SSLSocket
behaves like an NIO selectable
... hanging ...
OK, so this is the same bug as last time, could you mention it in https://github.com/oracle/truffleruby/issues/1527?
Seems like we made a lot of progress.
https://travis-ci.org/socketry/nio4r/jobs/555224139#L1020
Is I/O non-blocking or can we just ignore this? Or can you make it a no-op?
It looks like it's not stupid to make all I/O non-blocking. Ruby in theory handles this (i.e. IO#read
is implemented as a loop anyway).
The plan is to eventually try and merge https://bugs.ruby-lang.org/issues/14968
rb_io_set_nonblock
seems trivial to implement, it's probably enough to just call to Ruby: IO#nonblock= value
.
It looks like this is working pretty well, congratulations on getting it working.
I've added it to the travis test matrix, but there appear to be some issues.
https://travis-ci.org/socketry/nio4r/builds/466712901
cc @eregon (can you mention anyone else who might be able to help?)