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

Remote Jupyter Kernels started by VS Code do not have same names as Jupyter Notebook/Lab #13258

Closed
DonJayamanne opened this issue Apr 3, 2023 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug notebook-remote Applies to remote Jupyter Servers partner verified Verification succeeded
Milestone

Comments

@DonJayamanne
Copy link
Contributor

When starting a kernel session from VS Code (against AzML remote jupyter), then name of the session should be similar to what Jupyter notebook generates (today jupyter extension uses a GUID, as a result the links to open the notebook does not work in AzML)

@DonJayamanne DonJayamanne added the bug Issue identified by VS Code Team member as probable bug label Apr 3, 2023
@DonJayamanne DonJayamanne self-assigned this Apr 3, 2023
@DonJayamanne DonJayamanne added partner notebook-remote Applies to remote Jupyter Servers labels Apr 3, 2023
@DonJayamanne DonJayamanne added this to the May 2023 milestone Apr 28, 2023
@DonJayamanne
Copy link
Contributor Author

Let’s keep one issue, closing as a duplicate of #13424

@andreamah andreamah added the verified Verification succeeded label May 31, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 31, 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 notebook-remote Applies to remote Jupyter Servers partner verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

2 participants