-
Notifications
You must be signed in to change notification settings - Fork 293
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
Display a blank page after opening a ipynb file #1849
Comments
Thanks for the issue. Could you attach to this issue the notebook that is causing you to see the blank page to see if we can reproduce it? |
My file:
I found that there is a probability that the context is displayed. |
I was able to reproduce with this notebook, but only on the first launch of VS Code. Are you on the insiders version of the extension by the way? |
My VSCode version is 1.43.1 |
hey @jmew, where you able to reproduce this on Windows or on Linux? |
@DavidKutu sorry for the late reply, it was able to repro this on Windows |
I have the same problem: microsoft/vscode-python#11225. My case was closed, all my screenshot are there (#11225) |
I also have the same problem for at least 30 days. In fact, I feel it's getting worse but it's not consistent or measurable. My VSCode version is 1.44.2 |
I have the same problem and in fact it started to happen too often so it became impossible to work. Sadly I am forced to shift away from VSC+this plugin back to original JupyterLab until this issue is resolved. My bug is closed as a duplicate, but for reference here is its number https://github.com/microsoft/vscode-python/issues/11379 |
I have the same issue with Linux (vscode 1.44.2 + vscode-python 2020.4.76186). |
This is likely a dupe of #1062, which is currently being tracked as VS Code bug: microsoft/vscode#98335. |
Hello,
If I open a modified ipynb file, the editor displays a blank page.
If I use
>Python: Import Jupyter Notebook
, it will be imported in the cell mode.OS: Linux Python:3.7
how to fix/set it to normal jupyter notebook?
The text was updated successfully, but these errors were encountered: