Open davidvandebunte opened 10 months ago
Thanks for opening your first issue here! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out EBP's Code of Conduct. Also, please try to follow the issue template as it helps other community members to contribute more effectively.
If your issue is a feature request, others may react to it, to raise its prominence (see Feature Voting).
Welcome to the EBP community! :tada:
@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 read_data
should be JSON NOT NULL
and the order of the columns is different than in a regenerated cache. Still, this seems to be good enough so far.
Ah, you're quicker than me! For others, I created an alembic project to do this automatically: https://github.com/executablebooks/jupyter-cache-upgrader/tree/main/alembic
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