Total time is not the correct sum of tasks

[pyrareae]

I recently came across a strange bug. The total time for the day jumped down to zero after recording about an hour or so, then went up to 15 minutes over the course of about another hour of recording. This has only happened once so far, but it's pretty disconcerting knowing there might be something under the hood eating away at my recorded time. The details for the tasks show a completely different time than what's shown in the total time. Also the time recorded in the tasks jumps to different values depending on if I'm hovering over the time entry.

Your Environment

• Version used: SPA on Chrome
• Operating System and version: Windows 11
• Desktop Environment: n/a
• Browser Name and version: Google Chrome 120

Expected Behavior

The total time should be the sum of all tasks recorded for that day.

Current Behavior

Rarely the total time is a much smaller value than the actual sum of the tasks. Task time jumps around depending on mouse hover state.

Steps to Reproduce (for bugs)

Unknown.

Can you reproduce this reliably?

No

Screencast of behavior

chrome_sMsGth7pcD.mp4

chrome_Ear3opjUDX.mp4

[github-actions]

Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding!

[github-actions]

Hello there pyrareae! 👋

Thank you and congratulations 🎉 for opening your very first issue in this project! 💖

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀

For more open ended discussions and/or specific questions, please visit the discussions page. 💖

[johannesjo]

Thank you very much for reporting! So far I've been unable to reproduce this.

[pyrareae]

I'm wondering if this may have happened from accidentally having multiple instances open at once corrupting the time entries if they might have both been recording. I'm not sure what you're using as a data store but I could see that being problematic. I try to avoid having multiple instances open but I am using a multi-monitor setup spanning multiple virtual desktops and it's easy to not realize if the app is already open sometimes!

This is a bit of an off-topic suggestion but I wonder if you might add some kind of cross-instance bus via a BroadcastChannel and ping for other running instances during application startup, then bail out with a "there is already a running instance" type warning if there is a response from an already running instance.

[johannesjo]

This is a bit of an off-topic suggestion but I wonder if you might add some kind of cross-instance bus via a BroadcastChannel and ping for other running instances during application startup, then bail out with a "there is already a running instance" type warning if there is a response from an already running instance.

Could you open up a new issue for this?

[pyrareae]

Okay, opened #2987

[github-actions]

This issue has not received any updates in 90 days. Please comment, if this still relevant!