Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Choosing/changing remote local servers is buggy and confusing.

See original GitHub issue

Prep

Start a jupyter server (ala run jupyter notebook)
Start VS Code Insiders (I used build from 6/7/2022 and corresponding Jupyter extension)
Create a new notebook
Select a local kernel and run a simple cell

Bug 1

Run Jupyter: Specify Jupyter server for connections
Choose the server you created in the prep.
Press enter

I’m still connected to my local kernel. I expected to have to choose a new kernel.

Bug 2

Run Notebook: Select notebook kernel

The suggested kernel will be the local kernel I’m already connected to. I expect to either have no suggestion, or a suggestion from the server I just connected to.

Bug 3

Choose one of the server’s kernels, run a cell. All seems well.
Run Notebook: Select notebook kernel You’ll still see the local kernel suggested. Probably a dupe of Bug 2, but still.
Select the local kernel and run a cell.

You’ll run against the local kernel, yet the status bar says you’re connected to a Remote Jupyter server. Highly confusing.

Bug 4