Skip to content

When connecting to remote connection, if the default kernel doesn't start, then remote will never work in vscode #7384

Closed

Description

Basically we dont event dipslay the kernel picker that would allow users to connect toa different server.
The problem is we're starting a whole new session unnecessarily when all we want is a list of kernels.

I.e. even when we're getting list of kernels, we're starting unnecessary kernels.

Took me 2 hours to figure out that my default kernel wouldn't start.
I'm using Jupyter & jupyter labs & don't run into this issue, but vscode wouldn't allow me to connect to a local remote at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    bugIssue identified by VS Code Team member as probable bugnotebook-kernelKernels issues (start/restart/switch/execution, install ipykernel)notebook-remoteApplies to remote Jupyter Servers

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions