-
Notifications
You must be signed in to change notification settings - Fork 299
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
VS Code Insiders cannot open notebooks #4796
Comments
This comment has been minimized.
This comment has been minimized.
Same issue #4806 |
After the latest update of VS Code Insiders, the error message becomes "Unable to open 'IL_BC.ipynb': Cannot read property 'Markdown' of undefined.". Version: 1.54.0-insider (user setup) |
Same issue here:
|
The previous Insider version 1.53.0 works, which can be downloaded from https://vscode-update.azurewebsites.net/1.53.0-insider/win32-x64/insider (for Windows). In settings, search "update: Mode" and set it to "manual" to disallow automatic update. Different versions of VS code can co-exist but you need to start the specific version by double-clicking Code - Insiders.exe in the specific folder. |
For Apple Silicon Macs, the link you want is https://vscode-update.azurewebsites.net/1.53.0-insider/darwin-arm64/insider (it took me a few minutes to figure that out, so maybe that'll help others) |
For Linux (Ubuntu 20.04), got the .deb file for 1.53.0 from here. vscode-update.azurewebsites.net/1.53.0-insider/linux-deb-x64/insider |
This comment has been minimized.
This comment has been minimized.
For completeness: 1.53.0 Insider build for Intel Macs. |
You need to add -user to the download url if vscode is installed without local admin rights using user set-up, e.g.: |
Just an update, we are looking into this, and aware of the issues. |
Same issue - for now I'm working with the normal VSCode where notebooks are running. |
A new extension has been published to the marketplace with the fixes. |
Moving to validate |
For me I had to update the juypter extension and reload VS code for this to work with VS code insiders. |
Nope sorry still not working. See this issue: It works partially now. If you use the 'Open With' editor you can open a notebook in insiders again: |
Same for me. But at least this is usable for now. Thanks! |
Returned to 1.53.0 version on windows 10, also rolled back the jupyter extension which has also previously been updated and eveything got to work back again. Also turned off Vscode auto update and python auto update too for a while. |
After updating the Python extension and reinstaling the @DonJayamanne's VSIX extension, the Jupyter notebooks work here on VSCode 1.54 now, but I receive two errors from Python extension: |
It worked now, thank you! Too bad that VSCode Insiders with Jupyter Notebook (even if I always trusted the notebooks) does not support Jupyter Notebook's Python Markdown extension. |
@gusbemacbe Do you want to log a suggestion for this? |
Yes, I refer to the https://jupyter-contrib-nbextensions.readthedocs.io/en/latest/nbextensions/python-markdown/readme.html. |
After upgrading, notebooks are no longer detected but displayed as plain text in VSCode insiders. Any suggestions? |
Right click & "open with" did the job for me. |
Thanks! Should be fixed, though, so the regular approach works again. |
Working like a charm! Thanks all for the amazing extension. Do you have any idea when this new notebook interface should be released in VSCode's regular version? |
Yes it does! Thank you. |
Thanks notebooks work in 1.54. Is the live sharing of notebooks supposed to work? I never managed to get it working. Tips would be appreciated |
Live share of notebooks is a work in progress. You can track that here I believe: |
I'm closing this bug as the latest VS code insiders and the latest Jupyter extension and latest python insiders extension all seem to be working. Going forward we hope to be able to ship the jupyter extension more often to deal with breaking issues from VS code on a much quicker cadence. Thanks for your patience. |
@eduardopaul this is actively being pursued. We're working on testing it with a few customers first to see how the new version compares to the old one. Right now your best bet for using the new interface is to use the insiders version. |
@rchiodo, and Jupyter Notebook's Python Markdown extension? |
@gusbemacbe I suggest you log a new issue for the markdown extension. Until that happens we won't be able to tell how many other people want it. Meaning right now it's not planned at all. |
Notebooks broken in insiders
Since this version:
VS code insiders is making breaking changes to the proposed API the jupyter extension uses to open notebooks. Until we can get a new build out, we recommend going back to stable.
This issue will track our progress on making a new build just for insiders.
You can also go back to an older build of insiders if you want to continue using it. See directions here on how to do that:
microsoft/vscode#46089 (comment)
The text was updated successfully, but these errors were encountered: