Notebook validation failed
See original GitHub issueI am using jupyter 1.0.0 and ipywidgets 6.0.0 on Python3 and when I try to save my notebook after calling the display() function from IPython.display I get the following message:
Notebook validation failed: {‘model_id’: ‘211cc089c9134af79f0a8ccff7244ae8’} is not valid under any of the given schemas: { “model_id”: “211cc089c9134af79f0a8ccff7244ae8” }
Example code that gives the error:
from ipywidgets import FloatProgress
from IPython.display import display
a = FloatProgress(value=7.5,min=0,max=10.0)
display(a)
If I remove the call display(a) and save the file it raises no error.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
python 3.x - Notebook Validation Failed - Stack Overflow
Basically it says that there is something wrong in the cell 39 (index starts from 0, so 38+1) of the notebook. When I...
Read more >Notebook validation failed: Non-unique cell id #6001 - GitHub
In this case, the validation logic is encountering a duplicate cell-id that was previously, and randomly, generated 'waiting-opening' and ...
Read more >Notebook Validation Error | Data Science and Machine Learning
The error is while trying to validate the notebook which fails at a cell which plots plotly choropleth maps. The error looks like...
Read more >Notebook validation failed : PY-19610 - YouTrack
After editing .ipynb file in PyCharm using anaconda installation with ipython 4.2 I then opened the same file in jupiter using the same...
Read more >IPython Notebook Validation for py.test - Documentation ...
Command line usage · --nbval-lax , which collects notebooks and runs them, failing if there is an error. This mode does...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I found a solution to my problem:
From https://github.com/jupyter/nbformat/issues/161#issuecomment-574530127, by updating manually the
"nb_format_minor": 1to"nb_format_minor": 4the problem disappears.This is a bug that occurs with nbformat < 4.2. If you update nbformat, this should go away.