-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
Frames file reset without notice #499
Comments
That sounds quite worrying. I usually backup my frames file via a third party client in case something like this would happen, but haven't encountered it yet myself. What watson commands do you usually use? Do you mostly log data, or also work with reporting or any of the other subcommands? |
@joelostblom Hello, the commands I use daily are:
This reminds me that I sometimes forget to stop a frame and shutdown the computer, then stop it the next day with --at, and the first time I lost frames was actually one of those occurrences (can't say about the second one since I didn't notice it right away, but it could be). My watson version is 2.0.1 (speaking of which I'm going to upgrade to 2.1.0). |
Same here. Suddenly everything is gone, the backup file has been overwritten, too. Without a warning. I use the same commands as Manokha. Version 2.1.0 I was really happy with this too. And I am really not looking forward to use another browser based tool, again :( |
I lost all my frames twice recently. The first time I was very lucky:
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:
The text was updated successfully, but these errors were encountered: