You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks to contributors, with JupyterLab 4.0 using y-crdt related features, we already have the ability to read changes from files, and the next step is to let the Jupyter server take over the responsibility of writing code execution results.
To validate this idea, I implemented a simple generic client based on the websocket interface (I tried using jupyter_client's zmq interface, but it was hard to use), and then implemented a plugin with fileid support to implement this functionality.
Problem
Jupyter has been plaguing us with the problem of saving code output using the front-end for too long.
There is a lot of discussion about this here
jupyterlab/jupyterlab#12455
jupyterlab/jupyterlab#12867
jupyterlab/jupyterlab#2833
jupyter/notebook#641
Proposed Solution
Thanks to contributors, with JupyterLab 4.0 using y-crdt related features, we already have the ability to read changes from files, and the next step is to let the Jupyter server take over the responsibility of writing code execution results.
To validate this idea, I implemented a simple generic client based on the websocket interface (I tried using
jupyter_client
's zmq interface, but it was hard to use), and then implemented a plugin with fileid support to implement this functionality.client: https://github.com/Wh1isper/jupyter_kernel_client
extension: https://github.com/Wh1isper/jupyter_kernel_executor
Time is short, there is still a lot of content not perfect, looking forward to your suggestions
Additional context
I was inspired by the following projects and issues
#900
https://github.com/jupyter-server/jupyverse/
https://github.com/jupyter-server/jupyter_server_fileid
https://github.com/jupyter/nbformat
The text was updated successfully, but these errors were encountered: