-
Notifications
You must be signed in to change notification settings - Fork 294
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
Unable to connect using kernelpicker and existing jupyter server (notebook 7.x) #14215
Comments
@Yoyokrazy I'm not following you, whats the error message you get in VS Code?
I'm a little confused, based on your comments this used to work in the browser already. |
Never mind, I can replicate this. |
Closing as fixed in previous release, currently working in stable 🎉 |
Opening to make the code more resilient (future proof, rather than harcoding |
Anything to verify, since it seems the only change this month was stronger code? |
Oops it loaded the verified label after submitting that comment. |
@amunger @rebornix Will need this PR (#14391) and insiders released.
If this still does not work for local host we can create a separate issue, else this issue never gets resolved (this original issue was to do with a different reason for conections) |
verified as working with the steps listed above from @DonJayamanne, found issue mentioned below. |
Testing #14200
After using same steps, but on vsc insiders desktop, win64, was able to connect to the existing jupyter serverproperly and execute code.
Steps Taken:
newfile.ipynb
python -m jupyter lab --NotebookApp.allow_origin='*'
The text was updated successfully, but these errors were encountered: