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

Can't connect to Azure ML Jupyter server (with new remote experience) #11084

Closed
greazer opened this issue Aug 9, 2022 · 0 comments · Fixed by #11085
Closed

Can't connect to Azure ML Jupyter server (with new remote experience) #11084

greazer opened this issue Aug 9, 2022 · 0 comments · Fixed by #11085
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug triage-needed Issue needs to be triaged verified Verification succeeded
Milestone

Comments

@greazer
Copy link
Member

greazer commented Aug 9, 2022

  1. Ensure you have the new remote experience enabled: "jupyter.showOnlyOneTypeOfKernel": true,
  2. Open a notebook.
  3. Run the "Specify Jupyter Server for connections" command.
  4. Choose Azure ML Compute Instances.

You'll get this modal dialog. I should be presented with a list of subscriptions.

image

@greazer greazer added bug Issue identified by VS Code Team member as probable bug notebook-regression labels Aug 9, 2022
@github-actions github-actions bot added the triage-needed Issue needs to be triaged label Aug 9, 2022
@DonJayamanne DonJayamanne added this to the August 2022 milestone Aug 10, 2022
@connor4312 connor4312 added the author-verification-requested Issues potentially verifiable by issue author label Aug 25, 2022
@rzhao271 rzhao271 added verified Verification succeeded and removed author-verification-requested Issues potentially verifiable by issue author labels Aug 26, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 27, 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 triage-needed Issue needs to be triaged verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants