-
Notifications
You must be signed in to change notification settings - Fork 223
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
JEG kernels cannot be found as "Running" in Jupyter notebook #282
Comments
Thanks @charlieeeeeee . I spent some time with this and found it also occurs with "local" kernels (i.e., kernels that are local to JEG). I also found this to occur with the latest release of JKG. So I'm now a little suspicious that this is a client-side issue (with Notebook/nb2kg) but still need to take a closer look. |
Hmm - I just ran a pure Notebook (no nb2kg) and found that things work correctly and this is using I'm still leaving this issue closed relative to EG. This latest info just means that Notebook isn't necessarily the location to be poking around. |
@kevin-bates Right. I noticed the same behavior your comment regarding to "non-nb2kg" scenario. |
Spent some more time on this today and it seems like there must be something in the notebook in later releases that is side-affected when nb2kg is installed. However, in BOTH cases (older vs. newer NB versions), I find all the correct methods to return the list of running kernels getting called in nb2kg. Since these pages are a function of the js files, I suspect it's something within there - but don't know java script well enough to really tie the two (js and python) together. |
After narrowing this down, I found that the issue was introduced in Notebook I will open an issue in NB2KG and apply the fix there. cc: @charlieeeeeee |
Steps to reproduce:
Here are attached images of when issue occur for reference.
The text was updated successfully, but these errors were encountered: