Fix: Add missing metadata.widgets.state to broken notebooks #381
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes an issue where multiple Jupyter notebooks were missing the widgets.state in their metadata. This missing key caused notebooks to fail rendering properly on GitHub.
The fix adds an empty "state": {} object to each affected notebook’s widget metadata to conform with Jupyter notebook format requirements.
Fixes #376 and patches all affected notebooks, not just the one originally mentioned.
Type of change
How has this change been tested, please provide a testcase or example of how you tested the change?
Notebooks were checked if they rendered properly on Github without the invalid notebook error.
Any specific deployment considerations
None