You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tested with jruby-9.1.1.0 and nio4r 1.2.1
Under centOS (6.7 release)
If you execute the script shown in the linked issue, you'll see that the ruby IO system successfully registers events for a socket (IO.select). However, once you pass this "customized" IO object down to java land into an NIO channel, this is unable to register events on it.
By custom IO I mean initializing an IO object from an fd. This is common with some libraries imported through FFI which expose the file descriptor from some sort of structure. As soon as you use nio4r, which uses NIO channels, it blows. It all successfully works with MRI/libev.
The text was updated successfully, but these errors were encountered:
Coming from socketry/nio4r#94 (comment)
Environment
Tested with jruby-9.1.1.0 and nio4r 1.2.1
Under centOS (6.7 release)
If you execute the script shown in the linked issue, you'll see that the ruby IO system successfully registers events for a socket (IO.select). However, once you pass this "customized" IO object down to java land into an NIO channel, this is unable to register events on it.
By custom IO I mean initializing an IO object from an fd. This is common with some libraries imported through FFI which expose the file descriptor from some sort of structure. As soon as you use nio4r, which uses NIO channels, it blows. It all successfully works with MRI/libev.
The text was updated successfully, but these errors were encountered: