Kevin Bates

Results 510 comments of Kevin Bates

Today's [`ports_changed` exercise](https://github.com/jupyter-server/jupyter_server/pull/1088) got me thinking we should use 2.0 as a means of introducing a subclass to jupyter_client's `KernelManager` that the server's `MappingKernelManager` maintains instances of. (We've touched on...

Given the cross-post to `jupyter_client` I'm assuming this is still an issue. These symptoms are indicative of the kernel process starting just enough to satisfy the start kernel request, but...

Thanks for the additional information and for trying out papermill. You're right, this didn't reveal a whole lot. On the bright side, both scenarios are producing identical results. The initial...

Looking at the [`ipykernel` dependencies](https://github.com/ipython/ipykernel/blob/aa53dcef1a282cba7dbd06d0715252ad10a9987c/pyproject.toml#L27), they seem to be a good summary of what packages are involved in kernel communications. These would also apply to the notebook server (should it...

Ok. I don't expect the papermill-dependency exercise to yield anything since they are not common to those dependencies in the notebook/server code other than those same dependencies in ipykernel. That...

Thanks @adamjstewart. This (IMHO) implies the issue is probably at the sockets layer - which has some merit given that's a low-level area of the stack. I'm pinging @minrk in...

It's strange that `jupyter kernelspec list` is listing the `resources` directory here. I don't know what causes that and the path looks like it's the _package installation_ area for ipykernel...

Thanks for the response (and your patience)! This is helpful, although I still cannot determine the cause of the kernel's abrupt termination. I believe this issue should be investigated from...

> Papermill is sufficient to reproduce the issue, and it doesn't depend on ipykernel in any way, so it can't be the cause of the problem. How did you come...

ipykernel is not a direct dependency in the Python sense. nbclient doesn't call ipykernel methods directly. It issues _messages_ to configured ZMQ sockets (that the two processes know about via...