Skip to content
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.

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

Support multiple remote servers #9684

Closed
rebornix opened this issue Apr 14, 2022 · 2 comments
Closed

Support multiple remote servers #9684

rebornix opened this issue Apr 14, 2022 · 2 comments
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@rebornix
Copy link
Member

As part of the lazy kernel exploration microsoft/vscode#146942 (comment) , we want to support multiple remote servers, which would allow each notebook to use their preferred remote server, contributed by remote jupyter server provider.

@rebornix rebornix added bug Issue identified by VS Code Team member as probable bug and removed bug Issue identified by VS Code Team member as probable bug labels Apr 14, 2022
@rebornix rebornix added this to the April 2022 milestone Apr 14, 2022
@rchiodo rchiodo removed their assignment Apr 14, 2022
@DonJayamanne
Copy link
Contributor

While refactoring the kernel code I explored this task and at that point the plan was to add the Uri (some of remote connection info) into the kernel connection & when starting/connecting to the remote server we'd use that information instead of assuming the connections was in the single setting.

This was discussed with the team, however not completed. Can't remember why it wasn't completed, either ran out of time or just lost track of it. One use case was the ability to connect to multiple remotes and display in the kernel manager.

@DonJayamanne
Copy link
Contributor

Will not be done as we don't see the need to support multiple remotes for now.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

5 participants