`vim` crashes the Jupyter terminal when run in a split kernel configuration

bsyouness commented 2 weeks ago

We're getting crashes from the Jupyter terminal when lauching vim only with the split kernel.

Configuration

Jupyter server and Kernel running in separate containers.

Packages installed

vim installed on the Kernel side.

Replication steps

Open a Jupyter Terminal and run vim.

davidbrochart commented 2 weeks ago

I tried reproducing the bug, but I couldn't. What do you mean by crashes? Where does it happen? Any error message?

bsyouness commented 2 weeks ago

vimcrashes

davidbrochart commented 2 weeks ago

Could you show the content of the terminal (either the terminal where jupyter_server_terminals_proxy is running, or the one where JupyterLab's server is running)? Any error message will help.

bsyouness commented 1 week ago

The terminal where vim is running just crashes. So no logs to share there. Where are the other logs you're interested in?

davidbrochart commented 1 week ago

either the terminal where jupyter_server_terminals_proxy is running, or the one where JupyterLab's server is running

bsyouness commented 1 week ago

We're not getting any logs from the kernel or jupyverse apart from:

23982369-prj486ee3f515944c74905f9ece24b29ea9-75ce86a46d-pod kernel [2024-06-21 14:46:51,096 INFO] connection open
23982369-prj486ee3f515944c74905f9ece24b29ea9-75ce86a46d-pod kernel [I 240621 14:46:52 web:2348] 200 GET /kernels/3944fd4c-d4ea-4dad-bb97-144e88046425/has-process (127.0.0.1) 0.33ms
23982369-prj486ee3f515944c74905f9ece24b29ea9-75ce86a46d-pod kernel [I 240621 14:46:52 web:2348] 200 GET /kernels/3944fd4c-d4ea-4dad-bb97-144e88046425/poll (127.0.0.1) 0.34ms
23982369-prj486ee3f515944c74905f9ece24b29ea9-75ce86a46d-pod kernel [2024-06-21 14:46:52,440 INFO] connection closed

connection open corresponds to when I launch a terminal. When I type in vim and hit enter, it crashes and I get the connection closed event.

davidbrochart / jupyter_server_terminals_proxy