You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use a VM on a cloud server for many productivity things, the server is very budget and occasionally fills up completely with backups and such, I've never really bothered to remedy that situation with a better backup scheme or whatnot, because I'm using it so often it just kind of is a thing I can pretty easily work around.
When the server has no further disk space available and I then try to invoke topydo (specifically the prompt version if that makes a difference), it just totally lost my entire list.
Thankfully I was able to recover it by using tmux scrollback, but if not I'd really be up an ADHD creek.
Please look into this potentially day-ruining breaking bug.
I haven't dived into the code yet, but does the entire topydo app run the list in memory or something, and then try to write it back?
There really needs to be a check to ensure that at least the data isn't lost from when the app is launched, or maybe just refuse to launch if there's no disk space available?
The text was updated successfully, but these errors were encountered:
I use a VM on a cloud server for many productivity things, the server is very budget and occasionally fills up completely with backups and such, I've never really bothered to remedy that situation with a better backup scheme or whatnot, because I'm using it so often it just kind of is a thing I can pretty easily work around.
When the server has no further disk space available and I then try to invoke topydo (specifically the prompt version if that makes a difference), it just totally lost my entire list.
Thankfully I was able to recover it by using tmux scrollback, but if not I'd really be up an ADHD creek.
Please look into this potentially day-ruining breaking bug.
I haven't dived into the code yet, but does the entire topydo app run the list in memory or something, and then try to write it back?
There really needs to be a check to ensure that at least the data isn't lost from when the app is launched, or maybe just refuse to launch if there's no disk space available?
The text was updated successfully, but these errors were encountered: