emacs-jupyter/jupyter-client.el

1209 lines
52 KiB
EmacsLisp
Raw Normal View History

2017-12-14 13:39:30 -06:00
(require 'json)
2017-12-13 11:27:13 -06:00
(require 'zmq)
(eval-when-compile (require 'cl))
(require 'jupyter-channels)
(require 'jupyter-messages)
2017-12-14 13:39:30 -06:00
(declare-function string-trim-right "subr-x" (str))
2017-12-27 00:12:39 -06:00
(defvar jupyter--debug nil)
2017-12-14 13:39:30 -06:00
2017-12-13 11:27:13 -06:00
;;; Kernel client class
2017-12-22 00:50:56 -06:00
;;; Kernel manager
(defclass jupyter-connection ()
((session
:type jupyter-session
:initarg :session
:documentation "The `jupyter-session' object which holds the
key for authenticating messages.")
(conn-info
:type json-plist
:initarg :conn-info
:documentation "The connection plist which holds the channel
ports and other information required for connecting to a kernel.
See
http://jupyter-client.readthedocs.io/en/latest/kernels.html#connection-files"))
:abstract t)
(defclass jupyter-kernel-manager (jupyter-connection)
((name
:initarg :name
:type string)
(conn-file
:type (or null string))
2017-12-22 00:50:56 -06:00
(kernel
2017-12-13 11:27:13 -06:00
:type (or null process)
:initform nil
2017-12-15 18:14:28 -06:00
:documentation "The local kernel process or nil if no local
kernel was started by this client.")
2017-12-22 00:50:56 -06:00
(control-channel
:type (or null jupyter-control-channel)
:initform nil)
(kernel-info
:type (or null json-plist)
:initform nil
:documentation "Contains the result of an initial kernel_info_request
to the kernel after starting the kernel.")
(kernel-spec
:type (or null json-plist)
:initform nil)))
(cl-defmethod initialize-instance ((manager jupyter-kernel-manager) &rest slots)
(cl-call-next-method)
2017-12-22 00:50:56 -06:00
(unless (slot-boundp manager 'name)
(oset manager name "python")))
(defvar jupyter--kernelspec-dirs nil
"An alist matching kernel names to their kernelspec
directories.")
(defun jupyter-available-kernelspecs (&optional force-new)
(unless (or jupyter--kernelspec-dirs force-new)
(setq jupyter--kernelspec-dirs
(mapcar (lambda (s) (let ((s (split-string s " " 'omitnull)))
(cons (car s) (cadr s))))
(seq-subseq
(split-string
(shell-command-to-string "jupyter kernelspec list")
"\n" 'omitnull "[ \t]+")
1))))
jupyter--kernelspec-dirs)
(defun jupyter-find-kernelspec (prefix)
(when prefix
(let ((kname-path (cl-find-if
(lambda (s) (string-prefix-p prefix (car s)))
(jupyter-available-kernelspecs)))
(json-object-type 'plist)
(json-array-type 'list)
(json-false nil))
(when kname-path
(cons (car kname-path)
(json-read-file (expand-file-name
"kernel.json" (cdr kname-path))))))))
2017-12-22 00:50:56 -06:00
(cl-defun jupyter-create-connection-info (&key
(kernel-name "python")
(transport "tcp")
(ip "127.0.0.1")
(signature-scheme "hmac-sha256")
(key (jupyter--new-uuid))
(hb-port 0)
(stdin-port 0)
(control-port 0)
(shell-port 0)
(iopub-port 0))
"Create a jupyter connection plist.
The plist has the standard keys found in the jupyter spec. See
http://jupyter-client.readthedocs.io/en/latest/kernels.html#connection-files."
(unless (or (= (length key) 0)
(equal signature-scheme "hmac-sha256"))
(error "Only hmac-sha256 signing is currently supported."))
(append
(list :kernel_name kernel-name
:transport transport
:ip ip)
(when (> (length key) 0)
(list :signature_scheme signature-scheme
:key key))
(cl-loop
with sock = (zmq-socket (current-zmq-context) zmq-REP)
with addr = (concat transport "://" ip)
for (channel . port) in (list (cons :hb_port hb-port)
(cons :stdin_port stdin-port)
(cons :control_port control-port)
(cons :shell_port shell-port)
(cons :iopub_port iopub-port))
collect channel and
if (= port 0) do (setq port (zmq-bind-to-random-port sock addr))
and collect port and
do (zmq-unbind sock (zmq-socket-get sock zmq-LAST_ENDPOINT)) else
collect port
finally (zmq-close sock))))
2017-12-27 00:21:20 -06:00
(defun jupyter--kernel-sentinel (manager kernel event)
(cond
2017-12-30 23:35:04 -06:00
((cl-loop for type in '("exited" "failed" "finished" "killed" "deleted")
thereis (string-prefix-p type event))
2017-12-27 00:21:20 -06:00
(jupyter-stop-channels manager)
2017-12-30 23:35:04 -06:00
;; TODO: Only delete file when it hasn't been modified since it was created?
2017-12-27 00:21:20 -06:00
(delete-file (oref manager conn-file))
(oset manager kernel nil)
(oset manager conn-file nil)
(oset manager conn-info nil))))
(defun jupyter--start-kernel (kernel-name conn-file env args)
"Start a kernel.
A kernel named KERNEL-NAME is started using the connection
information in CONN-FILE. The name of the command used to start
the kernel subprocess should be the first element of ARGS and the
rest of the elements of ARGS are the command line parameters
passed to the command. If ENV is non-nil, then it should be a
plist containing environment variable names as keywords along
with their corresponding values. These will be set before
starting the kernel.
After the kernel reads CONN-FILE, CONN-FILE is renamed to
kernel-<pid>.json where <pid> is the process id of the kernel
subprocess.
The return value of this function is a cons cell
(NEW-CONN-FILE . PROC)
Where NEW-CONN-FILE is the renamed connection file and PROC is
the kernel subprocess."
(let* ((atime (nth 4 (file-attributes conn-file)))
(process-environment
(append
;; The first entry takes precedence when duplicated variables
;; are found in `process-environment'
(cl-loop
for e on env by #'cddr
for k = (car e)
for v = (cadr e)
collect (format "%s=%s" (cl-subseq (symbol-name k) 1) v))
process-environment))
(proc (apply #'start-process
(format "jupyter-kernel-%s" kernel-name)
nil (car args) (cdr args))))
(with-timeout
(10 (delete-file conn-file)
(delete-process proc)
(error "Kernel did not read connection file within timeout."))
(while (equal atime (nth 4 (file-attributes conn-file)))
(sleep-for 0 100)))
(let ((new-conn-file (expand-file-name
(format "kernel-%d.json" (process-id proc))
(file-name-directory conn-file))))
(rename-file conn-file new-conn-file)
(cons new-conn-file proc))))
2017-12-22 00:50:56 -06:00
;; TODO: Allow passing arguments like a different kernel file name or different
;; ports and arguments to the kernel
(cl-defmethod jupyter-start-kernel ((manager jupyter-kernel-manager))
2017-12-27 00:21:20 -06:00
"Start a kernel and associate it with MANAGER.
The MANAGER's `name' property is passed to
`jupyter-find-kernelspec' in order to find the kernel to start,
this means that `name' can be a prefix of a kernel name as well
as a full kernel name. For example, if `name' is \"julia\" it
will match the full kernel names \"julia-0.6\", \"julia-0.4\",
etc. The kernel used will be the first one matched from the list
of kernels returned by:
jupyter kernelspec list
If a valid kernel is found, its kernelspec is used to start a new
kernel. Starting a kernel involves the following steps:
1. Generating a new connection info with random ports for the
channels. See `jupyter-create-connection-info'.
2. Assigning a new `jupyter-session' to the MANAGER using the
generated key from the connection info. (TODO: Should first
start with generating a session key and then assigning it to
the connection info)
3. Writing the connection info to file
4. Starting a new subprocess kernel
5. Starting a control channel for the MANAGER to send
shutdown/interrupt requests"
2017-12-22 00:50:56 -06:00
(let ((kname-spec (jupyter-find-kernelspec (oref manager name))))
(unless kname-spec
(error "No kernel found that starts with name (%s)" (oref manager name)))
(cl-destructuring-bind (kernel-name . spec) kname-spec
;; Ensure we use the full name of the kernel
;; TODO: Require a valid kernel name when initializing the manager
(oset manager name kernel-name)
(oset manager kernel-spec spec)
(let* ((name (oref manager name))
(conn-info (jupyter-create-connection-info :kernel-name kernel-name))
(session-key (plist-get conn-info :key))
(conn-file (expand-file-name
(concat "kernel-" session-key ".json")
(string-trim-right (shell-command-to-string
"jupyter --runtime-dir")))))
(oset manager conn-info conn-info)
(oset manager session (jupyter-session :key session-key))
;; Write the connection file
2017-12-27 00:21:20 -06:00
(with-temp-file conn-file
2017-12-22 00:50:56 -06:00
(let ((json-encoding-pretty-print t))
2017-12-27 00:21:20 -06:00
(insert (json-encode-plist (oref manager conn-info)))))
(cl-destructuring-bind (new-conn-file . kernel)
(jupyter--start-kernel
kernel-name conn-file (plist-get spec :env)
(cl-loop
for arg in (plist-get spec :argv)
if (equal arg "{connection_file}") collect conn-file
else collect arg))
(oset manager conn-file new-conn-file)
(oset manager kernel kernel)
(set-process-sentinel
kernel (apply-partially #'jupyter--kernel-sentinel manager))
(jupyter-start-channels manager)
manager)))))
2017-12-22 00:50:56 -06:00
(cl-defmethod jupyter-start-channels ((manager jupyter-kernel-manager))
2017-12-27 00:21:20 -06:00
"Start a control channel on MANAGER."
2017-12-22 00:50:56 -06:00
(let ((control-channel (oref manager control-channel)))
(if control-channel
(unless (jupyter-channel-alive-p control-channel)
(jupyter-start-channel
control-channel
:identity (jupyter-session-id (oref manager session))))
(let ((conn-info (oref manager conn-info)))
(oset manager control-channel
(jupyter-control-channel
:endpoint (format "%s://%s:%d"
(plist-get conn-info :transport)
(plist-get conn-info :ip)
(plist-get conn-info :control_port))))
(jupyter-start-channels manager)))))
(cl-defmethod jupyter-stop-channels ((manager jupyter-kernel-manager))
2017-12-27 00:21:20 -06:00
"Stop the control channel on MANAGER."
2017-12-22 00:50:56 -06:00
(let ((control-channel (oref manager control-channel)))
(when control-channel
(jupyter-stop-channel control-channel)
(oset manager control-channel nil))))
(cl-defmethod jupyter-send ((manager jupyter-kernel-manager) type message)
2017-12-22 00:50:56 -06:00
(unless (member type '("shutdown_request" "interrupt_request"))
(error "Only shutdown or interrupt requests on control channel (%s)."
type))
(let ((session (oref manager session))
(sock (oref (oref manager control-channel) socket)))
(jupyter-send session sock type message)))
2017-12-22 00:50:56 -06:00
(cl-defmethod jupyter-stop-kernel ((manager jupyter-kernel-manager))
(when (jupyter-kernel-alive-p manager)
(jupyter-shutdown-request manager)
2017-12-27 00:21:20 -06:00
(with-timeout (5 (delete-process (oref manager kernel)))
2017-12-22 00:50:56 -06:00
(while (jupyter-kernel-alive-p manager)
2017-12-31 13:16:59 -06:00
(sleep-for 0 100)))))
2017-12-22 00:50:56 -06:00
(cl-defmethod jupyter-kernel-alive-p ((manager jupyter-kernel-manager))
(process-live-p (oref manager kernel)))
(cl-defmethod jupyter-shutdown-request ((manager jupyter-kernel-manager))
2017-12-22 00:50:56 -06:00
"Request a shutdown of MANAGER's kernel.
If RESTART is non-nil, request a restart instead of a complete shutdown."
2017-12-31 13:16:59 -06:00
;; FIXME: This shutdown request doesn't seem to work
(let ((msg (jupyter-message-shutdown-request)))
(jupyter-send manager "shutdown_request" msg)))
2017-12-22 00:50:56 -06:00
(cl-defmethod jupyter-interrupt-request ((manager jupyter-kernel-manager))
2017-12-22 00:50:56 -06:00
(if (equal (plist-get (oref manager kernel-spec) :interrupt_mode) "message")
(let ((msg (jupyter-message-interrupt-request)))
(jupyter-send manager "interrupt_request" msg))
2017-12-22 00:50:56 -06:00
(interrupt-process (oref manager kernel) t)))
;;; Kernel client class
(defclass jupyter-kernel-client (jupyter-connection)
((requests
2017-12-13 11:27:13 -06:00
:type hash-table
:initform (make-hash-table :test 'equal)
2017-12-13 11:27:13 -06:00
:documentation "A hash table with message ID's as keys. This
is used to register callback functions to run once a reply from
a previously sent request is received. See
`jupyter-add-callback'. Note that this is also used to filter
received messages that originated from a previous request by
this client. Whenever the client sends a message in which a
2017-12-15 18:14:28 -06:00
reply is expected, it sets an entry in this table to represent
the fact that the message has been sent. So if there is a
non-nil value for a message ID it means that a message has been
sent and the client is expecting a reply from the kernel.")
(ioloop
:type (or null process)
:initform nil
:documentation "The process which polls for events on all
live channels of the client.")
2017-12-13 11:27:13 -06:00
(shell-channel
:type (or null jupyter-shell-channel)
2017-12-13 11:27:13 -06:00
:initarg :shell-channel
:documentation "The shell channel.")
(iopub-channel
:type (or null jupyter-iopub-channel)
:initform nil
2017-12-13 11:27:13 -06:00
:initarg :iopub-channel
:documentation "The IOPub channel.")
(hb-channel
:type (or null jupyter-hb-channel)
:initform nil
2017-12-13 11:27:13 -06:00
:initarg :hb-channel
:documentation "The heartbeat channel.")
(stdin-channel
:type (or null jupyter-stdin-channel)
:initform nil
2017-12-13 11:27:13 -06:00
:initarg :stdin-channel
:documentation "The stdin channel.")))
2017-12-22 00:50:56 -06:00
(cl-defmethod jupyter-client-initialize-connection
((client jupyter-kernel-client)
file-or-plist)
"Read a connection FILE-OR-PLIST and return a `jupyter-kernel-client'.
If FILE-OR-PLIST is a file name, the connection info is read from
the file. If FILE-OR-PLIST is a plist, it is assumed to be a
connection plist containing the keys required for a connection
plist. See
http://jupyter-client.readthedocs.io/en/latest/kernels.html#connection-files."
(cl-check-type file-or-plist (or json-plist file-exists))
(let ((conn-info (let ((json-array-type 'list)
(json-object-type 'plist)
(json-false nil))
(if (json-plist-p file-or-plist) file-or-plist
(json-read-file file-or-plist)))))
(oset client conn-info conn-info)
(cl-destructuring-bind
(&key shell_port iopub_port stdin_port hb_port control_port ip
key transport signature_scheme kernel_name
&allow-other-keys)
conn-info
(when (and (> (length key) 0)
(not (functionp (intern signature_scheme))))
(error "Unsupported signature scheme: %s" signature_scheme))
;; Stop the channels if connected to some other kernel
(jupyter-stop-channels client)
(let ((addr (concat transport "://" ip)))
(oset client session (jupyter-session :key key))
(oset client stdin-channel
(make-instance
'jupyter-stdin-channel
2017-12-22 00:50:56 -06:00
:endpoint (format "%s:%d" addr stdin_port)))
(oset client shell-channel
(make-instance
'jupyter-shell-channel
2017-12-22 00:50:56 -06:00
:endpoint (format "%s:%d" addr shell_port)))
(oset client hb-channel
(jupyter-hb-channel
:endpoint (format "%s:%d" addr hb_port)))
(oset client iopub-channel
(make-instance
'jupyter-iopub-channel
2017-12-22 00:50:56 -06:00
:endpoint (format "%s:%d" addr iopub_port)))))))
(cl-defmethod initialize-instance ((client jupyter-kernel-client) &rest slots)
(let ((km (car (alist-get :kernel-manager slots))))
(if (not km) (cl-call-next-method)
2017-12-22 00:50:56 -06:00
(cl-check-type km jupyter-kernel-manager)
(jupyter-client-initialize-connection client (oref km conn-info))
client)))
2017-12-13 11:27:13 -06:00
2017-12-15 18:21:54 -06:00
;;; Lower level sending/receiving
(cl-defmethod jupyter-send ((client jupyter-kernel-client)
channel
type
message
&optional flags)
2017-12-15 18:21:54 -06:00
"Encode MESSAGE and send it on CLIENT's CHANNEL.
The message should have a TYPE corresponding to one of those
found in the jupyter messaging protocol. Optional variable FLAGS
are the flags sent to the underlying `zmq-send-multipart' call
using the CHANNEL's socket."
2017-12-15 18:21:54 -06:00
(declare (indent 1))
(zmq-subprocess-send (oref client ioloop)
(list 'send (oref channel type) type message flags))
;; Anything sent to stdin is a reply not a request so don't add it to
;; `:jupyter-pending-requests.'
(unless (eq (oref channel type) :stdin)
(let ((req (make-jupyter-request)))
(jupyter--ioloop-push-request client req)
req)))
2017-12-15 18:21:54 -06:00
(defun jupyter--ioloop (client)
(let ((iopub-channel (oref client iopub-channel))
(shell-channel (oref client shell-channel))
(stdin-channel (oref client stdin-channel)))
`(lambda (ctx)
(require 'jupyter-channels ,(locate-library "jupyter-channels"))
(require 'jupyter-messages ,(locate-library "jupyter-messages"))
;; We can splice the session object because it contains primitive types
(let* ((session ,(oref client session))
(iopub
(let ((sock (jupyter-connect-channel
:iopub ,(oref (oref client iopub-channel) endpoint)
(jupyter-session-id session))))
(zmq-socket-set sock zmq-SUBSCRIBE "")
sock))
(shell
(jupyter-connect-channel
:shell ,(oref (oref client shell-channel) endpoint)
(jupyter-session-id session)))
(stdin
(jupyter-connect-channel
:stdin ,(oref (oref client stdin-channel) endpoint)
(jupyter-session-id session)))
(channels (list (cons stdin :stdin)
(cons shell :shell)
(cons iopub :iopub)))
(priorities (list (cons :iopub 4)
(cons :stdin 4)
(cons :shell 2)))
(idle-count 0)
(queue (make-ring 10)))
(cl-flet ((send-recvd
()
;; Try and have a consistent order with which messages are
;; received in the parent process. We queue messages
;; received from the kernel and send them up to the parent
;; process only when (1) no messages have been received in
;; two polling periods or (2) when the queue is filled.
;; When sending, the messages are sorted by their send time
;; using the `:date' field of the message `:header'. In the
;; case that two messages have the same send time from the
;; kernel (i.e. when they don't have fractional resolution)
;; the messages are sorted by channel priority.
(cl-sort (cddr queue)
;; [<sorted non-nil elements> nil nil ...]
(lambda (a b)
(cond
((and (eq a nil) (eq a b)) t)
((eq a nil) nil)
((eq b nil) t)
(t
;; elements are (ctype idents . msg)
(let ((ta (jupyter-message-time (cddr a)))
(tb (jupyter-message-time (cddr b))))
(or (time-less-p ta tb)
(when (equal ta tb)
(> (alist-get (car a) priorities)
(alist-get (car b) priorities)))))))))
(cl-loop
while (not (ring-empty-p queue))
do (zmq-prin1 (cons 'recvd (ring-remove queue)))))
(recv-message
(sock ctype)
(when (= (ring-length queue) (ring-size queue))
(send-recvd))
(ring-insert queue (cons ctype (jupyter-recv session sock))))
(send-message
(sock ctype rest)
(zmq-prin1
(cons 'sent
(cons ctype (apply #'jupyter-send session sock rest)))))
(start-channel
(sock)
(zmq-connect
sock (zmq-socket-get sock zmq-LAST_ENDPOINT))
(zmq-poller-register
(current-zmq-poller) sock zmq-POLLIN))
(stop-channel
(sock)
(zmq-poller-unregister (current-zmq-poller) sock)
(condition-case err
(zmq-disconnect
sock (zmq-socket-get sock zmq-LAST_ENDPOINT))
(zmq-ENOENT nil)
(error (signal (car err) (cdr err))))))
(condition-case nil
(with-zmq-poller
;; Also poll for standard-in events to be able to read commands
;; from the parent emacs process without blocking
(zmq-poller-register (current-zmq-poller) 0 zmq-POLLIN)
(mapc (lambda (x) (zmq-poller-register (current-zmq-poller)
(car x)
zmq-POLLIN))
channels)
(unwind-protect
(while t
(when (and (= idle-count 2)
(> (ring-length queue) 0))
(send-recvd))
(let ((events (condition-case err
(zmq-poller-wait-all (current-zmq-poller) 5 20)
(zmq-EINTR nil)
;; TODO: For any other kind of error,
;; just reset the polling loop by exiting
;; `with-zmq-poller'.
(error (signal (car err) (cdr err))))))
(if (null events) (setq idle-count (1+ idle-count))
(setq idle-count 0)
(when (alist-get 0 events)
(setf (alist-get 0 events nil 'remove) nil)
(cl-destructuring-bind (cmd . data)
(zmq-subprocess-read)
(cl-case cmd
(quit
(signal 'quit nil))
(start-channel
(let* ((ctype data)
(sock (car (rassoc ctype channels))))
(start-channel sock)))
(stop-channel
(let* ((ctype data)
(sock (car (rassoc ctype channels))))
(stop-channel sock)))
(send
(let* ((ctype (car data))
(sock (car (rassoc ctype channels)))
(rest (cdr data)))
(send-message sock ctype rest))))))
(cl-loop for (sock . event) in events
do (recv-message
sock (alist-get sock channels))))))
(mapc (lambda (s)
(zmq-socket-set s zmq-LINGER 0)
(zmq-close s))
(mapcar #'car channels))))
(quit (zmq-prin1 (cons 'quit (cons nil nil))))))))))
(defun jupyter--ioloop-pop-request (client)
(let* ((ring (process-get (oref client ioloop) :jupyter-pending-requests))
(req (ring-remove ring)))
req))
(defun jupyter--ioloop-push-request (client req)
(let* ((ioloop (oref client ioloop))
(ring (or (process-get ioloop :jupyter-pending-requests)
(let ((ring (make-ring 10)))
(process-put ioloop :jupyter-pending-requests ring)
ring))))
(ring-insert+extend ring req 'grow)))
2017-12-27 00:00:59 -06:00
(defun jupyter--ioloop-sentinel (client ioloop event)
(cond
2017-12-30 23:35:04 -06:00
((cl-loop for type in '("exited" "failed" "finished" "killed" "deleted")
thereis (string-prefix-p type event))
2017-12-27 00:00:59 -06:00
(kill-buffer (process-buffer ioloop))
(when (jupyter-channel-alive-p (oref client hb-channel))
(jupyter-stop-channel (oref client hb-channel)))
(oset client ioloop nil))))
2017-12-13 11:27:13 -06:00
(defun jupyter--ioloop-filter (client event)
(cl-destructuring-bind (ctype . data) (cdr event)
(cl-case (car event)
2017-12-27 00:00:59 -06:00
;; Cleanup handled in sentinel
(quit)
(sent
(when jupyter--debug
(message "SEND: %s" data))
(unless (eq ctype :stdin)
;; Anything sent on stdin is a reply and therefore never added to
;; `:jupyter-pending-requests'
(let ((id data)
(req (jupyter--ioloop-pop-request client)))
(setf (jupyter-request--id req) id)
(puthash id req (oref client requests)))))
(recvd
(when jupyter--debug
(message "RECV: %s %s %s"
(jupyter-message-type (cdr data))
(jupyter-message-parent-id (cdr data))
(jupyter-message-content (cdr data))))
(let ((channel (cl-find-if (lambda (c) (eq (oref c type) ctype))
(mapcar (lambda (x) (eieio-oref client x))
'(stdin-channel
shell-channel
iopub-channel)))))
(jupyter-channel-push-message channel data)
(run-with-timer 0.001 nil #'jupyter-handle-message client channel))))))
2017-12-13 11:27:13 -06:00
(cl-defmethod jupyter-start-channels ((client jupyter-kernel-client)
&key (shell t)
(iopub t)
(stdin t)
2017-12-15 18:14:43 -06:00
(control t)
2017-12-13 11:27:13 -06:00
(hb t))
2017-12-15 18:14:28 -06:00
"Start the pre-configured channels of CLIENT.
This function calls `jupyter-start-channel' for every channel
that has a non-nil value passed to this function. All channels
are started by default, so to prevent a channel from starting you
would have to pass a nil value for the channel's key. As an
example, to prevent the control channel from starting you would
call this function like so
(jupyter-start-channels client :control nil)
In addition to calling `jupyter-start-channel', a subprocess is
created for each channel which monitors the channel's socket for
input events. Note that this polling subprocess is not created
for the heartbeat channel."
(unless (oref client ioloop)
(when hb (jupyter-start-channel (oref client hb-channel)))
(oset client ioloop
(zmq-start-process
(jupyter--ioloop client)
2017-12-27 00:00:59 -06:00
(apply-partially #'jupyter--ioloop-filter client)
(apply-partially #'jupyter--ioloop-sentinel client)))))
2017-12-13 11:27:13 -06:00
2017-12-19 18:13:42 -06:00
(cl-defmethod jupyter-stop-channels ((client jupyter-kernel-client))
"Stop any running channels of CLIENT."
(when (oref client hb-channel)
(jupyter-stop-channel (oref client hb-channel)))
2017-12-19 18:13:42 -06:00
(let ((ioloop (oref client ioloop)))
(when ioloop
(zmq-subprocess-send ioloop (cons 'quit nil))
2017-12-27 00:00:59 -06:00
(with-timeout (1 (delete-process ioloop))
(while (oref client ioloop)
(sleep-for 0 100))))))
2017-12-13 11:27:13 -06:00
2017-12-15 18:14:28 -06:00
(cl-defmethod jupyter-channels-running-p ((client jupyter-kernel-client))
"Are any channels of CLIENT alive?"
2017-12-13 11:27:13 -06:00
(cl-loop
for channel in (list 'shell-channel
'iopub-channel
'hb-channel
'stdin-channel)
if (jupyter-channel-alive-p (eieio-oref client channel))
return t))
;;; Message callbacks
2017-12-13 11:27:13 -06:00
;; A `jupyter-request' object represents the status of a request to the kernel
;; and holds all the information required to process the messages associated
;; with the request. Whenever a message arrives that is associated with a
;; request's `jupyter-request-id', any callbacks associated with the message
;; type are run (see `jupyter-add-callback'). When a request's
;; `jupyter-idle-received-p' property is non-nil, then it signifies that the
;; request has been handled by the kernel.
(cl-defstruct jupyter-request
(-id)
(idle-received-p)
(callbacks))
(cl-defstruct jupyter-callback
(ran-p nil)
(cb nil))
(defun jupyter-request-id (req)
(with-timeout (0.5 (error "Request not processed."))
(while (null (jupyter-request--id req))
(sleep-for 0 10)))
(jupyter-request--id req))
(defun jupyter--run-callbacks-for-message (req msg)
2017-12-31 13:16:59 -06:00
"Run the MSG callbacks of REQ.
The return value is non-nil if any handler methods for MSG should
be run. If this function returns nil, then it indicates that no
handler methods should be run for MSG. If there are multiple
callbacks for a MSG then if at least one of them returns non-nil,
this function will also return non-nil."
(when req
(let* ((callbacks (jupyter-request-callbacks req))
(cbt (cdr (assoc t callbacks)))
(cb (cdr (assoc (jupyter-message-type msg) callbacks))))
2017-12-31 13:16:59 -06:00
(if (or cb cbt) (cl-find-if
(lambda (a) (not (null a)))
(cl-loop
for cb in (list cb cbt)
when cb collect
(funcall (jupyter-callback-cb cb) msg)
and do (setf (jupyter-callback-ran-p cb) t)))
t))))
(defun jupyter-add-callback (msg-type req function)
2017-12-31 13:16:59 -06:00
"Add callback FUNCTION for a message REQUEST.
FUNCTION will be run for all received messages that are
associated with REQ and have a message type of MSG-TYPE. The
CLIENT handler method for MSG-TYPE is prevented from running if
FUNCTION returns nil. Otherwise if FUNCTION returns a non-nil
value, the handler method for MSG-TYPE is run. This allows for a
mechanism to silently consume messages without passing them to
the handler methods which are usually run for updating
user-interface elements of the CLIENT.
2017-12-13 11:27:13 -06:00
2017-12-31 13:16:59 -06:00
As a special case if MSG-TYPE is t, the callback function is run
for all received messages associated with REQ.
As an example, suppose you want to register a callback when you
recieve an `execute-reply' after sending an execute request. This
can be done like so:
2017-12-15 18:14:28 -06:00
(jupyter-add-callback 'execute-reply
2017-12-15 18:14:28 -06:00
(jupyter-request-execute client :code \"y = 1 + 2\")
(lambda (msg)
(cl-assert (equal (jupyter-message-type msg) \"execute_reply\"))))
Note that the callback is given the raw decoded message received
from the kernel without any processing done to it."
(declare (indent 2))
(let ((mt (plist-get jupyter--received-message-types msg-type)))
(if mt (setq msg-type mt)
;; msg-type = t means to run for every message type associated with
;; msg-id
(unless (eq msg-type t)
(error "Not a valid received message type (`%s')" msg-type))))
(if (jupyter-request-idle-received-p req)
(error "Request already received idle message.")
(let ((callbacks (jupyter-request-callbacks req))
(cb (make-jupyter-callback :cb function)))
(if (null callbacks)
(setf (jupyter-request-callbacks req) (list (cons msg-type cb)))
(let* ((cb-for-type (assoc msg-type callbacks)))
(if cb-for-type (setcdr cb-for-type cb)
(nconc callbacks (list (cons msg-type cb)))))))))
(defun jupyter-wait-until (msg-type req timeout cond)
2017-12-15 18:18:41 -06:00
"Wait until COND returns non-nil for a received message.
COND is run for every received message that has a type of
MSG-TYPE and whose parent header has a message ID of PMSG-ID. If
no messages are received that pass these two conditions before
TIMEOUT (in seconds), this function returns nil. Otherwise it
returns the received message. Note that if TIMEOUT is nil, it
defaults to 1 second."
(declare (indent 3))
(setq timeout (or timeout 1))
(cl-check-type timeout number)
2017-12-15 18:18:41 -06:00
(lexical-let ((msg nil)
(cond cond))
(jupyter-add-callback msg-type req
(lambda (m) (setq msg (when (funcall cond m) m))))
(with-timeout (timeout nil)
(while (null msg)
(sleep-for 0.01))
msg)))
2017-12-15 18:18:41 -06:00
(defun jupyter-wait-until-idle (req &optional timeout)
"Wait until TIMEOUT for REQ to receive an idle message.
If TIMEOUT is non-nil, it defaults to 1 second."
(jupyter-wait-until 'status req timeout #'jupyter-message-status-idle-p))
2017-12-15 18:18:41 -06:00
(defun jupyter-wait-until-received (msg-type req &optional timeout)
2017-12-31 13:16:59 -06:00
"Wait for a message with MSG-TYPE to be received by CLIENT.
2017-12-14 13:48:39 -06:00
This function waits until CLIENT receives a message from the
kernel that satisfies the following conditions:
2017-12-13 11:27:13 -06:00
2017-12-14 13:48:39 -06:00
1. The message has a type of MSG-TYPE
2. The parent header of the message has a message ID of PMSG-ID
Note that MSG-TYPE should be one of the keys found in
`jupyter--recieved-message-types'. If it is not, an error is
raised.
All of the `jupyter-request-*' functions return a message ID that
2017-12-14 13:48:39 -06:00
can be passed to this function as the PMSG-ID. If the message
associated with PMSG-ID is not expecting to receive a message
with MSG-TYPE, this function will wait forever so be sure that
you are expecting to receive a message of a certain type after
sending one. For example you would not be expecting an
`execute-reply' when you send a kernel info request with
`jupyter-request-kernel-info', but you would be expecting a
2017-12-14 13:48:39 -06:00
`kernel-info-reply'. See the jupyter messaging specification for
more info
http://jupyter-client.readthedocs.io/en/latest/messaging.html"
(declare (indent 1))
(jupyter-wait-until msg-type req timeout #'identity))
2017-12-13 11:27:13 -06:00
(defun jupyter--handle-message (client channel)
2017-12-13 11:27:13 -06:00
"Process a message on CLIENT's CHANNEL.
When a message is received on CLIENT's channel it is decoded and
added to the CHANNEL's recv-queue and this function is scheduled
to be run at a later time to process the messages in the queue.
To process a message the following steps are taken:
1. A message is removed from the recv-queue
2. A handler function is found base on CHANNEL's type
2017-12-31 13:16:59 -06:00
3. Any callbacks previously registered for the message are run
4. The handler method for the message is called. Note that if any
of the callbacks return a value of nil, the handler method for
the message is not run. This allows for consuming messages
without passing them to the handler methods which are usually
run to update user interface elements.
5. This function is scheduled to process another message of
CHANNEL in the future"
2017-12-13 11:27:13 -06:00
(let ((ring (oref channel recv-queue)))
(unless (ring-empty-p ring)
2017-12-15 22:33:56 -06:00
;; Messages are stored like (idents . msg) in the ring
(let* ((ctype (oref channel type))
2017-12-13 11:27:13 -06:00
(handler (cl-case ctype
2017-12-14 14:03:58 -06:00
(:stdin #'jupyter--handle-stdin-message)
(:iopub #'jupyter--handle-iopub-message)
(:shell #'jupyter--handle-shell-message)
(:control #'jupyter--handle-control-message)
(otherwise (error "Wrong channel type (%s)." ctype))))
(msg (cdr (ring-remove ring)))
(pmsg-id (jupyter-message-parent-id msg))
(requests (oref client requests))
(req (gethash pmsg-id requests)))
;; Drop messages not sent by us.
;; TODO: Some messages might be useful.
(when req
(when (jupyter-message-status-idle-p msg)
(setf (jupyter-request-idle-received-p req) t))
(unwind-protect
(funcall handler client req msg)
(unwind-protect
(jupyter--run-callbacks-for-message req msg)
;; Remove the request once an idle message has been received and
;; all callbacks have run atleast once. This is done because it
;; is not gauranteed that the idle message is received after all
;; other messages for a request.
;;
;; NOTE: this probably doesn't handle all cases.
(when (and (jupyter-request-idle-received-p req)
;; Check if all callbacks for req have run at least
;; once
(if (not (jupyter-request-callbacks req)) t
(cl-loop
for (reply-type . cb) in (jupyter-request-callbacks req)
unless (jupyter-callback-ran-p cb) return nil
finally return t)))
(remhash pmsg-id requests)))))))))
2017-12-13 11:27:13 -06:00
2017-12-14 14:11:42 -06:00
;;; Received message handlers
2017-12-13 11:27:13 -06:00
;;; stdin messages
(defun jupyter--handle-stdin-message (client req msg)
;;; STDIN message requests/handlers
2017-12-13 11:27:13 -06:00
(cl-destructuring-bind (&key prompt password &allow-other-keys)
(plist-get msg :content)
(jupyter-handle-input client req prompt password)))
2017-12-13 11:27:13 -06:00
(cl-defmethod jupyter-handle-input-reply ((client jupyter-kernel-client) req prompt password)
2017-12-15 18:14:28 -06:00
"Handle an input request from CLIENT's kernel.
PROMPT is the prompt the kernel would like to show the user. If
PASSWORD is non-nil, then `read-passwd' is used to get input from
the user. Otherwise `read-from-minibuffer' is used."
;; TODO: Allow for quiting the input request. In this case, I suppose send an
;; interrupt request to the kernel
2017-12-13 11:27:13 -06:00
(let ((channel (oref client stdin-channel))
(msg (jupyter-message-input-reply
2017-12-13 11:27:13 -06:00
:value (funcall (if password #'read-passwd
#'read-from-minibuffer)
prompt))))
;; TODO: Check for 'allow_stdin'
;; http://jupyter-client.readthedocs.io/en/latest/messaging.html#stdin-messages
(jupyter-send client channel "input_reply" msg)))
2017-12-13 11:27:13 -06:00
2017-12-14 13:32:29 -06:00
;;; control messages
(defun jupyter--handle-control-message (client req msg)
2017-12-14 13:32:29 -06:00
(cl-destructuring-bind (&key msg_type content &allow-other-keys) msg
2017-12-19 11:54:10 -06:00
(let ((status (plist-get content :status)))
(if (equal status "ok")
2017-12-31 13:16:59 -06:00
;; FIXME: An interrupt reply is only sent when interrupt_mode is set
2017-12-19 11:54:10 -06:00
;; to message in a kernel's kernelspec.
(pcase msg_type
("interrupt_reply"
(jupyter-handle-interrupt client req)))
2017-12-19 11:54:10 -06:00
(if (equal status "error")
(error "Error (%s): %s"
(plist-get content :ename) (plist-get content :evalue))
(error "Error: aborted"))))))
;;; CONTROL message requests/handlers
2017-12-14 13:32:29 -06:00
(cl-defmethod jupyter-shutdown-request ((client jupyter-kernel-client) &optional restart)
2017-12-15 18:14:28 -06:00
"Request a shutdown of CLIENT's kernel.
2017-12-14 13:32:29 -06:00
If RESTART is non-nil, request a restart instead of a complete shutdown."
(let ((channel (oref client shell-channel))
(msg (jupyter-message-shutdown-request :restart restart)))
(jupyter-send client channel "shutdown_request" msg)))
2017-12-14 13:32:29 -06:00
(cl-defmethod jupyter-handle-shutdown-reply ((client jupyter-kernel-client) req restart)
"Default shutdown reply handler.")
2017-12-19 11:54:10 -06:00
;; FIXME: This breaks the convention that all jupyter-request-* functions
;; returns a message-id future object.
;; (cl-defmethod jupyter-request-interrupt ((client jupyter-kernel-client))
;; ;; TODO: Check for interrupt_mode of the kernel's kernelspec
;; ;; http://jupyter-client.readthedocs.io/en/latest/messaging.html#kernel-interrupt
;; (let ((channel (oref client control-channel)))
;; (jupyter-send client channel "interrupt_request" ())))
(cl-defmethod jupyter-handle-interrupt-reply ((client jupyter-kernel-client) req)
2017-12-31 13:16:59 -06:00
"Default interrupt reply handler.")
2017-12-14 13:32:29 -06:00
;;; SHELL message requests/handlers
2017-12-13 11:27:13 -06:00
;; http://jupyter-client.readthedocs.io/en/latest/messaging.html#messages-on-the-shell-router-dealer-channel
(defun jupyter--handle-shell-message (client req msg)
2017-12-13 11:27:13 -06:00
(cl-destructuring-bind (&key msg_type content &allow-other-keys) msg
(let ((status (plist-get content :status)))
;; We check for error or abort since "is_complete_reply" also contains a
;; status field
(if (not (member status '("error" "abort")))
2017-12-13 11:27:13 -06:00
(pcase msg_type
("execute_reply"
(cl-destructuring-bind (&key execution_count
user_expressions
payload
&allow-other-keys)
content
(jupyter-handle-execute-reply
client req execution_count user_expressions payload)))
("inspect_reply"
(cl-destructuring-bind (&key found
data
metadata
&allow-other-keys)
content
(jupyter-handle-inspect-reply
client req found data metadata)))
("complete_reply"
(cl-destructuring-bind (&key matches
cursor_start
cursor_end
metadata
&allow-other-keys)
content
(jupyter-handle-complete-reply
client req matches cursor_start cursor_end metadata)))
("history_reply"
(cl-destructuring-bind (&key history &allow-other-keys)
content
(jupyter-handle-history-reply client req history)))
("is_complete_reply"
(cl-destructuring-bind (&key status indent &allow-other-keys)
content
(jupyter-handle-is-complete-reply client req status indent)))
("comm_info_reply"
(cl-destructuring-bind (&key comms &allow-other-keys)
content
(jupyter-handle-comm-info-reply client req comms)))
("kernel_info_reply"
(cl-destructuring-bind (&key protocol_version
implementation
implementation_version
language_info
banner
help_links
&allow-other-keys)
content
(jupyter-handle-kernel-info-reply
client req protocol_version implementation implementation_version
language_info banner help_links)))
2017-12-13 11:27:13 -06:00
(_ (error "Message type not handled yet.")))
2017-12-31 13:16:59 -06:00
;; FIXME: Do something about errrors here?
;; (if (equal status "error")
;; (error "Error (%s): %s"
;; (plist-get content :ename) (plist-get content :evalue))
;; (error "Error: aborted"))
))))
2017-12-13 11:27:13 -06:00
(cl-defmethod jupyter-execute-request ((client jupyter-kernel-client)
&key code
(silent nil)
(store-history t)
(user-expressions nil)
(allow-stdin t)
(stop-on-error nil))
2017-12-15 18:14:28 -06:00
"Send an execute request."
2017-12-13 11:27:13 -06:00
(declare (indent 1))
(let ((channel (oref client shell-channel))
(msg (jupyter-message-execute-request
2017-12-13 11:27:13 -06:00
:code code
:silent silent
:store-history store-history
:user-expressions user-expressions
:allow-stdin allow-stdin
:stop-on-error stop-on-error)))
(jupyter-send client channel "execute_request" msg)))
2017-12-13 11:27:13 -06:00
(cl-defmethod jupyter-handle-execute-reply ((client jupyter-kernel-client)
req
execution-count
user-expressions
payload)
"Default execute reply handler.")
(cl-defmethod jupyter-inspect-request ((client jupyter-kernel-client)
&key code
(pos 0)
(detail 0))
2017-12-15 18:14:28 -06:00
"Send an inspect request."
(declare (indent 1))
(let ((channel (oref client shell-channel))
(msg (jupyter-message-inspect-request
:code code :pos pos :detail detail)))
(jupyter-send client channel "inspect_request" msg)))
(cl-defmethod jupyter-handle-inspect-reply ((client jupyter-kernel-client)
req
found
data
metadata)
"Default inspect reply handler.")
(cl-defmethod jupyter-complete-request ((client jupyter-kernel-client)
&key code
(pos 0))
2017-12-15 18:14:28 -06:00
"Send a complete request."
(declare (indent 1))
(let ((channel (oref client shell-channel))
(msg (jupyter-message-complete-request
:code code :pos pos)))
(jupyter-send client channel "complete_request" msg)))
(cl-defmethod jupyter-handle-complete-reply ((client jupyter-kernel-client)
req
matches
cursor-start
cursor-end
metadata)
"Default complete reply handler.")
(cl-defmethod jupyter-history-request ((client jupyter-kernel-client)
&key
output
raw
2017-12-27 00:18:00 -06:00
(hist-access-type "tail")
session
start
stop
2017-12-27 00:18:00 -06:00
(n 10)
pattern
unique)
2017-12-15 18:14:28 -06:00
"Send a history request."
(declare (indent 1))
(let ((channel (oref client shell-channel))
(msg (jupyter-message-history-request
:output output
:raw raw
:hist-access-type hist-access-type
:session session
:start start
:stop stop
:n n
2017-12-17 02:58:11 -06:00
:pattern pattern
:unique unique)))
(jupyter-send client channel "history_request" msg)))
(cl-defmethod jupyter-handle-history-reply ((client jupyter-kernel-client) req history)
"Default history reply handler.")
(cl-defmethod jupyter-is-complete-request ((client jupyter-kernel-client)
&key code)
2017-12-15 18:14:28 -06:00
"Send an is-complete request."
(declare (indent 1))
(let ((channel (oref client shell-channel))
(msg (jupyter-message-is-complete-request
:code code)))
(jupyter-send client channel "is_complete_request" msg)))
(cl-defmethod jupyter-handle-is-complete-reply
((client jupyter-kernel-client) req status indent)
"Default is complete reply handler.")
(cl-defmethod jupyter-comm-info-request ((client jupyter-kernel-client)
&key target-name)
2017-12-15 18:14:28 -06:00
"Send a comm-info request."
(declare (indent 1))
(let ((channel (oref client shell-channel))
(msg (jupyter-message-comm-info-request
:target-name target-name)))
(jupyter-send client channel "comm_info_request" msg)))
(cl-defmethod jupyter-handle-comm-info-reply ((client jupyter-kernel-client) req comms)
"Default comm info. reply handler.")
(cl-defmethod jupyter-kernel-info-request ((client jupyter-kernel-client))
2017-12-15 18:14:28 -06:00
"Send a kernel-info request."
(let* ((channel (oref client shell-channel))
(msg (jupyter-message-kernel-info-request)))
(jupyter-send client channel "kernel_info_request" msg)))
2017-12-13 11:27:13 -06:00
(cl-defmethod jupyter-handle-kernel-info-reply ((client jupyter-kernel-client)
req
protocol-version
implementation
implementation-version
language-info
banner
help-links)
"Default kernel-info reply handler.")
2017-12-13 11:27:13 -06:00
;;; IOPUB message handlers
2017-12-13 11:27:13 -06:00
(defun jupyter--handle-iopub-message (client req msg)
(let ((content (jupyter-message-content msg)))
(pcase (jupyter-message-type msg)
2017-12-19 11:54:10 -06:00
("shutdown_reply"
(cl-destructuring-bind (&key restart &allow-other-keys)
content
(jupyter-handle-shutdown-reply client req restart)))
("stream"
(cl-destructuring-bind (&key name text &allow-other-keys)
content
(jupyter-handle-stream client req name text)))
("execute_input"
(cl-destructuring-bind (&key code execution_count &allow-other-keys)
content
(jupyter-handle-execute-input client req code execution_count)))
("execute_result"
(cl-destructuring-bind (&key execution_count
data
metadata
&allow-other-keys)
content
(jupyter-handle-execute-result client req execution_count data metadata)))
("error"
(cl-destructuring-bind (&key ename evalue traceback &allow-other-keys)
content
(jupyter-handle-error client req ename evalue traceback)))
("status"
(cl-destructuring-bind (&key execution_state &allow-other-keys)
content
(jupyter-handle-status client req execution_state)))
("clear_output"
(cl-destructuring-bind (&key wait &allow-other-keys)
content
(jupyter-handle-clear-output client req wait)))
("display_data"
(cl-destructuring-bind (&key data metadata transient &allow-other-keys)
content
(jupyter-handle-display-data client req data metadata transient)))
("update_display_data"
(cl-destructuring-bind (&key data metadata transient &allow-other-keys)
content
(jupyter-handle-update-display-data client req data metadata transient)))
2017-12-13 11:27:13 -06:00
(_ (error "Message type not handled yet.")))))
(cl-defmethod jupyter-handle-stream ((client jupyter-kernel-client) req name text)
"Default stream handler.")
2017-12-13 11:27:13 -06:00
(cl-defmethod jupyter-handle-execute-input ((client jupyter-kernel-client)
req
2017-12-13 11:27:13 -06:00
code
execution-count)
"Default execute input handler.")
(cl-defmethod jupyter-handle-execute-result ((client jupyter-kernel-client)
req
execution-count
data
metadata)
"Default execute result handler.")
(cl-defmethod jupyter-handle-error ((client jupyter-kernel-client)
req
ename
evalue
traceback)
"Default error handler.")
2017-12-27 21:07:36 -06:00
(cl-defmethod jupyter-handle-status ((client jupyter-kernel-client) req execution-state)
"Default status handler.")
(cl-defmethod jupyter-handle-clear-output ((client jupyter-kernel-client) req wait)
"Default clear output handler.")
(cl-defmethod jupyter-handle-display-data ((client jupyter-kernel-client)
req
data
metadata
transient)
"Default display data handler.")
(cl-defmethod jupyter-handle-update-display-data ((client jupyter-kernel-client)
req
data
metadata
transient)
"Default update display data handler.")
2017-12-13 11:27:13 -06:00
(provide 'jupyter-client)