emacs-jupyter/jupyter

Is it possible to kill remote kernels

Open

#213 opened on Feb 12, 2020

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Emacs Lisp (106 forks)auto 404
help wanted

Repository metrics

Stars
 (1,028 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Hi,

I have worked out how to run a remote kernel at NERSC via ssh. First, I run

ssh jkitchin@nersc "jupyter kernel --kernel=myenv" which creates a kernel,

and then I connect to it like this

#+BEGIN_SRC jupyter-python :session /ssh:nersc:/global/u2/j/jkitchin/.local/share/jupyter/runtime/kernel-13bd20a9-e77f-411a-ba13-c33526716961.json import sys print(sys.path) #+END_SRC

this works, but I wondered if there is a way to kill this kernel remotely. It turns out that just killing the ssh command does not do that, it leaves the kernel running on the server.

update: ssh -t jkitchin@nersc "jupyter kernel --kernel=myenv" does kill the kernel when I kill the ssh command.

I still wonder if it could be done by elisp in jupyter.el

Contributor guide

Research direction
Investigate how jupyter.el currently manages kernel processes, including local and remote kernels. Look for existing commands that kill kernels and see how they handle SSH sessions. Consider how the workaround using `ssh t` could be incorporated into the Elisp code. Examine the relevant code paths and test with a remote kernel.
Tech stack
shell
Domain
developer experiencetooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitEmacs LispJupyterSSH
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65