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
If you star and unstar a bunch of emails very fast, you might corrupt the todo file, like this:
2019-11-09 Security alert for your linked Google Account email/id:t_caNytfAQbvLKagENsatLwdXMQ3EEuGULe3fh1KF59 @emailmail
2019-11-09 Security alert for your linked Google Account email/id:t_caNytfAQbvLKagENsatLwdXMQ3EEuGULe3fh1KF59 @email
Note the duplicated id and the corrupted @emailmail context. I think this is because there are multiple concurrent reads and writes to the file when emails are (un)starred in quick succession. Perhaps all the functions manipulating the file should act transactionally with respect to the file.
The text was updated successfully, but these errors were encountered:
I was able to reproduce the corrupted contexts by unstarring nine emails at once though multi-selection, followed by right-clicking and selecting "Remove Stars." I have yet to reproduce the todo-duplication.
Now, every save/remove of a to-do from the todo.txt is put in a queue which allows only one of those operations at a time.
The reason for this change is described in issue #1. It doesn't fix that issue completely, though.
In the unstable branch:
Note the duplicated id and the corrupted
@emailmail
context. I think this is because there are multiple concurrent reads and writes to the file when emails are (un)starred in quick succession. Perhaps all the functions manipulating the file should act transactionally with respect to the file.The text was updated successfully, but these errors were encountered: