Notebooks - Kernel Not Saved

[claudiaregio]

• VS Code Version: 1.63.2
• OS Version: Windows 11

Steps to Reproduce:

1. Create notebook
2. Select kernel and write code/run cells
3. Save notebook
4. Kernel selection disappears

I started working on an analysis and when I got to a checkpoint I was happy with I saved the notebook. After saving I tried to keep working and started getting errors in my notebook and it took me a few minutes to realize the kernel was not saved so I had to select it again and rerun everything to get back to where I was, a pretty annoying papercut

[roblourens]

Is there already an issue for this? We've discussed this but I can't find it. Need to figure out how to transfer a kernel registration from an untitled document to another one which we don't have a straightforward way to do.

[claudiaregio]

I could have sworn I had opened this issue in the past but could not find it for the life of me so I just filed it again😆

[claudiaregio]

Any chance there is an update on this?

[rebornix]

When the untitled notebook is saved, the kernel and language info are saved to disk but the Jupyter extension won't use the previously selected kernel as preferred kernel. Though if you create an untitled notebook again, you will get the same kernel.

[DonJayamanne]

As discussed, labelling as upstream vscode, as the kernel selection is maintained in vscode core and the selected kernel needs to be transitioned upon saving as another file.

[DonJayamanne]

This should be fixed now, closing this for verification