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 have encountered a bug in the "Stopwatch" feature. It sometimes restarts a stopwatch, after I already stopped it.
I assume that this happens when the view is closed/terminated, before the "stop event" (or whatever the correct term is) is sent to the rust-backend. The best method I found to reproduce is:
Start a stopwatch
Let the stopwatch run for some time
Stop the stopwatch
Close the view manually, by using the "overview" button of the phone and closing the app
Re-open activitywatch
The stopwatch runs again
This does not trigger the bug 100%, so I would assume that there is some racing condition or the operation takes some time. My assumptions would have been that after pressing stop, the termination is directly "committed", but this does not seem to be the case.
The bug also happens, when I don't close the view manually, just by switching to another app.
ActivityWatch: v.0.10.0 (rust) (Installed over Google playstore)
Android: 8.0.0 (Samsung Galaxy S7)
The text was updated successfully, but these errors were encountered:
I have encountered a bug in the "Stopwatch" feature. It sometimes restarts a stopwatch, after I already stopped it.
I assume that this happens when the view is closed/terminated, before the "stop event" (or whatever the correct term is) is sent to the rust-backend. The best method I found to reproduce is:
This does not trigger the bug 100%, so I would assume that there is some racing condition or the operation takes some time. My assumptions would have been that after pressing stop, the termination is directly "committed", but this does not seem to be the case.
The bug also happens, when I don't close the view manually, just by switching to another app.
ActivityWatch: v.0.10.0 (rust) (Installed over Google playstore)
Android: 8.0.0 (Samsung Galaxy S7)
The text was updated successfully, but these errors were encountered: