Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
DonJayamanne opened this issue Sep 1, 2021 · 3 comments
Closed

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

DonJayamanne opened this issue Sep 1, 2021 · 3 comments
Labels
bug Issue identified by VS Code Team member as probable bug notebook-execution Kernels issues (start/restart/switch/execution, install ipykernel) notebook-remote Applies to remote Jupyter Servers
Milestone
January 2022

Comments

@DonJayamanne
Copy link
Contributor

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.
@DonJayamanne DonJayamanne added the bug Issue identified by VS Code Team member as probable bug label Sep 1, 2021
@greazer greazer added kernel-enumeration notebook-remote Applies to remote Jupyter Servers and removed needs-triage labels Sep 2, 2021
@greazer
Copy link
Member

greazer commented Sep 2, 2021

We shouldn't need to start a kernel to get the list of kernels in the remote scenario.

@greazer greazer added this to the October 2021 milestone Sep 2, 2021
@claudiaregio claudiaregio mentioned this issue Sep 4, 2021
Closed
@DonJayamanne DonJayamanne mentioned this issue Oct 12, 2021
Closed
1 task
@rchiodo rchiodo modified the milestones: October 2021, November 2021 Oct 27, 2021
@greazer greazer added the notebook-execution Kernels issues (start/restart/switch/execution, install ipykernel) label Oct 27, 2021
@zpincus zpincus mentioned this issue Nov 4, 2021
Closed
2 tasks
@rchiodo rchiodo modified the milestones: November 2021, January 2022 Dec 6, 2021
@DonJayamanne
Copy link
Contributor Author

This has been fixed in the Nov milestome.

@DonJayamanne
Copy link
Contributor Author

This has been fixed and validated in a previous release

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Issue identified by VS Code Team member as probable bug notebook-execution Kernels issues (start/restart/switch/execution, install ipykernel) notebook-remote Applies to remote Jupyter Servers
Projects
None yet
Milestone
January 2022
Development

No branches or pull requests
3 participants
@DonJayamanne @greazer @rchiodo