Skip to content
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

Closed
charlieeeeeee opened this issue Mar 20, 2018 · 6 comments
Closed

JEG kernels cannot be found as "Running" in Jupyter notebook #282

charlieeeeeee opened this issue Mar 20, 2018 · 6 comments
Assignees
Labels

Comments

@charlieeeeeee
Copy link
Contributor

Steps to reproduce:

  1. Launch notebook and JEG
  2. Start remote kernel (Kernel is started and responsive)
  3. While the kernels are still alive and running. Navigate to the main menu and observe the notebook icon is not GREEN (which suppose to be green, to show active/running kernel)
  4. Verify this by clicking on the "Running" tab. No running notebook is found.

Here are attached images of when issue occur for reference.

5662ad78c09a4d14
bb73ce0619484c4

@kevin-bates
Copy link
Member

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.

@kevin-bates kevin-bates changed the title JEG remote kernels cannot be found as "Running" in Jupyter notebook JEG kernels cannot be found as "Running" in Jupyter notebook Mar 20, 2018
@kevin-bates kevin-bates self-assigned this Mar 24, 2018
@kevin-bates
Copy link
Member

Well, it appears as though somewhere between Notebook 4.3.1 and 5.2.1 this functionality broke. I haven't tried any versions in between these two but have confirmed that in 4.3.1 the following is produced:
screen shot 2018-03-23 at 5 26 04 pm
while in versions later than 5.2.1 (and perhaps earlier), the running kernels do not show up.

As a result, this should be deemed a Notebook issue and I'm marking as Invalid relative to Enterprise Gateway.

@kevin-bates
Copy link
Member

Hmm - I just ran a pure Notebook (no nb2kg) and found that things work correctly and this is using 5.4.0. As a result, this implies that its something in the NB stack and possibly affected by the nb2kg extension (sigh).

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.

@charlieeeeeee
Copy link
Contributor Author

@kevin-bates Right. I noticed the same behavior your comment regarding to "non-nb2kg" scenario.

@kevin-bates
Copy link
Member

kevin-bates commented Mar 24, 2018

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.

@kevin-bates
Copy link
Member

After narrowing this down, I found that the issue was introduced in Notebook 5.1.0.rc1 (Notebook 5.0.0 behaves fine). Looking at the various changes, it looks like this PR is where things get messed up for nb2kg because it doesn't return the type column from row_to_model() and that PR now discriminates on that value.

I will open an issue in NB2KG and apply the fix there.

cc: @charlieeeeeee

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants