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.

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

For Azure ML remote compute instances, the kernel sessions created on VS Code should be reusable on JupyterLab and AzNotebooks #13424

Closed
Tracked by #13427
sevillal opened this issue Apr 28, 2023 · 1 comment · Fixed by #13504
Closed
Tracked by #13427

For Azure ML remote compute instances, the kernel sessions created on VS Code should be reusable on JupyterLab and AzNotebooks #13424

sevillal opened this issue Apr 28, 2023 · 1 comment · Fixed by #13504
Assignees
@DonJayamanne
Labels
author-verification-requested Issues potentially verifiable by issue author bug Issue identified by VS Code Team member as probable bug partner verified Verification succeeded

Comments

@sevillal
Copy link
Contributor

When user is connected to an Azure ML compute instance in VS Code and a new kernel session needs to be created, then the kernel session created on VS Code is a reusable session in JupyterLab and Azure ML and there is one session per notebook.

This might be fixed by #13258 but we need to confirm.
@sevillal sevillal added the bug Issue identified by VS Code Team member as probable bug label Apr 28, 2023
@amunger amunger assigned DonJayamanne and unassigned amunger Apr 28, 2023
@sevillal sevillal mentioned this issue Apr 28, 2023
Closed
8 tasks
@DonJayamanne DonJayamanne mentioned this issue Apr 28, 2023
Closed
@DonJayamanne DonJayamanne mentioned this issue Apr 28, 2023
Closed
2 tasks
@kieferrm kieferrm mentioned this issue May 8, 2023
Closed
6 tasks
DonJayamanne added a commit that referenced this issue May 15, 2023
@DonJayamanne
Minor kernel picker fixes (for #13424)
b2415bb
@DonJayamanne DonJayamanne mentioned this issue May 16, 2023
Merged
@DonJayamanne DonJayamanne mentioned this issue May 16, 2023
Merged
@DonJayamanne DonJayamanne added the author-verification-requested Issues potentially verifiable by issue author label May 28, 2023
@minsa110 minsa110 mentioned this issue May 30, 2023
Closed
@sevillal sevillal added the verified Verification succeeded label May 31, 2023
@sevillal
Copy link
Contributor Author

Verified.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@DonJayamanne DonJayamanne

Labels
author-verification-requested Issues potentially verifiable by issue author bug Issue identified by VS Code Team member as probable bug partner verified Verification succeeded
Projects
None yet
Milestone
No milestone
3 participants
@DonJayamanne @amunger @sevillal