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

[Feature Request](or question) List connection info of all kernels #6936

Closed
fecet opened this issue Jun 20, 2023 · 2 comments
Closed

[Feature Request](or question) List connection info of all kernels #6936

fecet opened this issue Jun 20, 2023 · 2 comments

Comments

@fecet
Copy link

fecet commented Jun 20, 2023

Open as suggested in #6307 (comment). For a opened notebook, we can use

%connect_info

to see its connect info and its correspoding json file. Is there any way to get this without opening every notebook and type this command?

I know all connect info json are located in $HOME/.local/share/jupyter/runtime but I cannot distinguish them by notebooks and they seems will not be cleaned automaticlly after jupyter closed.

To be more clear, I want something like

../dir1/notebook1.ipynb  python 3.8(env1)  kernel-0e32...json
../dir1/notebook2.ipynb  python 3.8(env1)  kernel-7b63...json
../dir2/notebook3.ipynb  python 3.10(env2)  kernel-53c3...json
...

as described in lkhphuc/jupyter-kernel.nvim#9

I can track this by filtering jupyer's log, but it would be better if notebook can provide a command to do so.

@fecet fecet added the bug label Jun 20, 2023
@jupyterlab-probot jupyterlab-probot bot added the status:Needs Triage Applied to issues that need triage label Jun 20, 2023
@RRosio RRosio added enhancement and removed bug status:Needs Triage Applied to issues that need triage labels Jun 20, 2023
@RRosio
Copy link
Collaborator

RRosio commented Jun 20, 2023

Hi @fecet thank you for submitting this issue! It might be a good idea to start this off as an extension that depending on demand can later be moved to JupyterLab or IPython.

@fecet
Copy link
Author

fecet commented Jun 21, 2023

I tried to solve this problem on my own today jupyter/jupyter_client#953. Can someone help review it?

@fecet fecet closed this as completed Jun 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants