-
-
Notifications
You must be signed in to change notification settings - Fork 249
Open
Description
I lost all my frames twice recently. The first time I was very lucky:
- I realised that I lost them before attempting any new watson "writing" commands (didn't know it would have ended up overwriting backup file then)
- I found the backup file and could overwrite current file with backup without issue, then reapplied the time frame that had been lost in the process
I though then that I would have access to a backup file when such things happen and moved on.
Yesterday, I lost all my frames again, but this time I realised it only one week after the loss. And frames.bak had been overwritten (probably a lot of times) since then.
Which means I lost 4 months of time frames with no way of retrieving them.
Maybe I missed an error/warning message of some sort but:
- Frames should never be dropped without at least warning the user
- frames.bak should never be overwritten if it results in frames loss (overwrite if old.start >= current.start and old.end <= current.end)
- I'd rather lose my last few commands than months or more of data
Metadata
Metadata
Assignees
Labels
No labels