About this project

[Wh1isper]

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

Help with the project

Looking forward to help with this project in the following areas

1. Maintenance: I know GitHub has a series of Actions and other ways to help maintain the repository, but I lack the time and experience to do so
2. Testing: Currently, only basic unit tests are available, if possible, add some tests for fileid and JupyterLab 4.0 scenarios
3. Front-end: I have no front-end related knowledge, but if it is possible to implement a button to execute cell, should be an exciting improvement
4. Others: Any ideas and suggestions for this project are welcome

[Wh1isper]

Welcome discussion here: jupyter-server/jupyter_server#1123