Open DillonJ opened 1 year ago
It doesn't work as in the UI doesn't respond? You are unable to show the commit dialog? You commit via the dialog but changes do not stick in the DB?
(you have a lot of errors in those tracebacks that are probably related to a lot of toolbox activity (removing things in db editor, stoping tools, etc)
I'm not a huge fan of implementing a recovery path that could also have its own issues - seems better to me to spend the effort in fixing the commit itself. Anyways, we do have some sort of recovery path which is Hamburger -> Export to create another sqlite or json file that then could be reimported - have you tried that?
The dialog opens - I type a message press ok and nothing happens - it fails silently and the asterix beside the db name doesn't go away
Maybe related: https://github.com/irena-flextool/flextool/issues/32
Very often, after working on a SpineDB and I go to commit the changes, it doesn't work. It happens often after interrupting a workflow execution but I'm not sure if that is always the case. I have the below errors in the console.
This has happened alot over the lifetime of toolbox, where I have a current SpineDB with a lot of changes to it and I can't commit them and am forced to redo them all again. I suppose it's been for many different reasons. Is there anyway we can salvage a db with changes that haven't been committed yet? Like write some sort of recovery file or something like that? Some fallback?