Validation Issue when opening .ipynb file in other .ipynb editors (Jupyter Notebook)
See original GitHub issueEnvironment data
- VS Code version: 1.43.2
- Extension version (available under the Extensions sidebar): 2020.3.69010
- OS and version: Windows 10 Home 10.0.18363 Build 18363
- Python version (& distribution if applicable, e.g. Anaconda): 3.7.6 anaconda
- Type of virtual environment used (N/A | venv | virtualenv | conda | …): conda
- Relevant/affected Python packages and their versions: XXX
- Relevant/affected Python-related VS Code extensions and their versions: XXX
- Jedi or Language Server? (i.e. what is
"python.jediEnabled"
set to; more info microsoft/vscode-python#3977): Disabled - Value of the
python.languageServer
setting: Microsoft
Expected behaviour
The file is expetected to open normally in Jupyter Notebook
Actual behaviour
Upon opening the .ipynb file this validation error occurs.
Notebook validation failed: Additional properties are not allowed (‘outputs’, ‘execution_count’ were unexpected): { “cell_type”: “markdown”, “metadata”: {}, “source”: “# Comp9417 - Homework 2\n## Question 2”, “execution_count”: null, “outputs”: [] }
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
- Use Vscode to open a .ipynb file.
- Work as per usual.
- Open file that was being edited in vscode in jupyter notebook in google chrome.
Produces this validation error.
Notebook validation failed: Additional properties are not allowed (‘outputs’, ‘execution_count’ were unexpected): { “cell_type”: “markdown”, “metadata”: {}, “source”: “# Comp9417 - Homework 2\n## Question 2”, “execution_count”: null, “outputs”: [] }
Logs
Output for Python
in the Output
panel (View
→Output
, change the drop-down the upper-right of the Output
panel to Python
)
XXX
Output from Console
under the Developer Tools
panel (toggle Developer Tools on under Help
; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging
)
XXX
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (3 by maintainers)
Top GitHub Comments
Hi @DavidKutu
I will try and replicate the scenario as best as i can but it can be inconsistent. Im not really sure how to do this step " to get to a markdown cell with outputs and execution time?". I’m not sure that, that is the issue. It seems that when I start a ipynb file in vscode and then try and open it in jupyter notebook, jupyter notebook complains that this is not a valid file. I can send you a test file if you would like ? I believe that there is some issue with the actual save functionality of vscode but I can only speculate.
How would I get into the insiders build ?
cheers for following up on this.
Validated. I’m not able to create the markdown cells with execution_count or output anymore.