-
Notifications
You must be signed in to change notification settings - Fork 14
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
Migrating cached notebooks to >= 0.5.0 #113
Comments
Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗 |
@davidvandebunte before you re-execute, I think it should be possible to manually upgrade the database. From the CHANGELOG, it appears that the table name changed, and the schema includes some new fields. I think if we make those changes by hand, we should be in luck. |
Thanks @agoose77! As you suggested it wasn't all that difficult: ALTER TABLE `nbstage` RENAME TO `nbproject`;
ALTER TABLE nbproject ADD COLUMN read_data JSON;
ALTER TABLE nbproject ADD COLUMN exec_data JSON; The schema doesn't match perfectly: so far I've noticed that |
Ah, you're quicker than me! For others, I created an alembic project to do this automatically: As ever, please please please back up the cache before trying this or any other surgery! |
Describe the bug
Thanks for this great project and for Jupyter Book! Obviously many of the same people work on both projects.
After upgrading to a recent version of this package, I'm getting the error:
Reproduce the bug
It seems likely this is a known issue. See jupyter-cache/CHANGELOG.md and the breaking change mention of
nbstage
andnbproject
.Unfortunately I've got many notebooks that take hours to execute and use R packages that don't produce completely reliable i.e. reproducible results 🙄 (see e.g. Practice: Chp. 14).
I've not found a way to avoid re-execution and so for now I'm planning to attempt to rebuild the cache over a day or two. I'd just like to confirm there's likely no other way around this problem.
List your environment
The text was updated successfully, but these errors were encountered: