-
Notifications
You must be signed in to change notification settings - Fork 33
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
Socket timeout when attempting to connect to iruby kernel #363
Comments
Hi @edsinclair Unfortunately, the IRuby project does not have any active developers. I occasionally merge pull requests sent from volunteers, even though I don't understand the details of IRuby's implementation very well. Are you using Ruby version 3.4? Currently, Ruby 3.4 does not pass the tests, so it may not work for several months until someone contributes a pull request... If you are using a different version, it might be possible to get it working. |
Hmm? |
@kojix2 thanks for the response. I'm using Ruby 3.3.6 installed using
The
I'm wondering if it has something to do with zeromq and Mac OS firewall settings... but that is the only idea I can think of right now. |
I just verified that the python process spawns a ruby process when I attempt to open a notebook with the ruby kernel: ![]() But for some reason the ruby process stays pegged at 100% CPU, which would seem to be a symptom closely related to the socket timeout... A second python process is spawned when I open a notebook with the python kernel, but after an initial CPU usage spike it drops to an idle state. @kojix2 when you open a ruby notebook do you get this same WARN line in your log?
|
A quick update. I've been trying to run this from a directory with a Gemfile and I decided to clear out all the gems except for iruby, ffi-rzmq and that resulted in the ability for the notebook to connect to the Ruby kernel. Now I have a different error that appears in the notebook output when I attempt to execute ruby code (In this case a simple puts statement)
|
@kojix2 So it looks like So the handling in eval here: https://github.com/SciRuby/iruby/blob/master/lib/iruby/backend.rb#L64 |
@edsinclair |
For others who might find this thread in the future. The original problem was caused by the presence of the activesupport gem in the Gemfile of the directory I starting my notebook server from. Removing it and re-bundling allowed the ruby kernel to start without getting stuck at 100% CPU. And with the fix in #364 I have a working notebook 🙌 |
I'm attempting to run a notebook on MacOS Sonoma. I've followed the installation instructions and attempted to troubleshoot but am stuck. The python kernel is working fine, but the ruby kernel never connects. This is the contents of the log:
Any suggestions for troubleshooting this would be most welcome. Thanks.
The text was updated successfully, but these errors were encountered: