Using !connect jupyter, Python process created by VS Code is left orphan once closing a notebook

[ruxo]

Describe the bug

I've installed Anaconda on my machine and connected the notebook using the provided directive:

#!connect jupyter --kernel-name pythonkernel --conda-env base --kernel-spec python3

Following the instructions, I created a Raw Value Storage cell, placed this directive in it, and executed it. This allowed me to create other Python cells using the new kernel.

However, I noticed an issue when renaming the .dib file. When VS Code reopens the renamed file, the Python process created during the notebook's execution is left orphaned. The same issue occurs when I close VS Code while working with the notebook—leaving behind a running Python process. It seems like these processes are not being properly cleaned up upon file renaming or closing VS Code.

Please complete the following:

Which version of .NET Interactive are you using? (In a notebook, run the #!about magic command. ):

Version: 1.0.556801+2d9726b514498cd84403a1d5d13da3161c99eab2
Library version: 1.0.0-beta.24568.1+2d9726b514498cd84403a1d5d13da3161c99eab2
Build date: 2024-11-28T02:23:58.7753388Z

• OS
  • Windows 11
  • Windows 10
  • macOS
  • Linux (Please specify distro)
  • iOS
  • Android
• Browser
  • Chrome
  • Edge
  • Firefox
  • Safari
• Frontend
  • Jupyter Notebook
  • Jupyter Lab
  • nteract
  • Visual Studio Code
  • Visual Studio Code Insiders
  • Visual Studio
  • Other (please specify)

Screenshots