Selected remote Jupyter kernel not kept after closing VS Code

[fra-luc]

Bug: Notebook Editor, Interactive Window, Editor cells

Steps to cause the bug to occur

1. Connect to remote Jupyter server
2. Choose one among the kernels available on the server
3. Close VS Code
4. Reopen VS Code

Actual behavior

Kernel is not the one chosen anymore; seemingly VS Code changed it to the first of the available kernels
( you need to choose the original kernel manually again in order to work with it )

Expected behavior

I would expect the selected kernel, at least at project level, even better at notebook level, to not change after restarting.

Your Jupyter and/or Python environment

Please provide as much info as you readily know

• Jupyter server running: Remote
• Extension version: 2020.6.91350
• VS Code version: 1.46.1 cd9ea6488829f560dc949a8b2fb789f3cdc05f5d x64
• Setting python.jediEnabled: true | false (can't find setting but languageServer is Jedi)
• Setting python.languageServer: Jedi
• Python and/or Anaconda version: conda 4.5.12
• OS: Linux Ubuntu 18.04 both server and local
• Virtual environment: conda

Developer Tools Console Output

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl

[greazer]

Hi @fra-luc, sorry we didn't responsd, but we are planning on addressing this in our next release (or possibly the one thereafter).

[IanMatthewHuff]

Validated. Swapped the kernel after remote connection and this connection was preserved across the next time I connected after closing and reopening VSCode.