-
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
Cannot open resource with notebook editor #4845
Comments
Thanks for the bug. The problem should go away if you try a second time. Can you check if you have this entry in your settings.json?
That should only be enabled in the insiders version of VS code. If you're using the stable version of VS code you shouldn't have that value there. |
I do have that entry in my settings.json. I have two Macs that are synced on the same vscode settings, and one is using the insiders version and one is using the stable version. The stable version one is showing this error. Do you think the shared settings between the two is causing the issue? |
Maybe? I thought insiders and stable wouldn't share the same settings but if they did it would cause the problem. |
OK, I commented out that block and it works on my Stable version but not the Insiders one. The insiders one is showing "Cannot read property 'Code' of Undefined". |
This is actually this bug here: #4796. Insiders is not currently working for opening notebooks. VS code made some breaking API changes that we haven't caught up to yet. |
OK, so I don't know why:
is appearing in my stable build. But I am changing this locally for now in my stable build (by removing it and setting it to |
If a user has the editorAssociations setting, then opt them into the native notebook editor experiment. |
Validated, did use settings sync but must updated the settings manually |
I cannot open Jupyter Notebooks from the explorer window at the moment. I get the following error. However, if I right-click and "Open in Notebook Editor", the Jupyter notebook opens well. Is there a reason or setting for this?
The text was updated successfully, but these errors were encountered: