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
So today I noticed that my wakatime dashboard was reporting numbers much higher than I felt like they should've been, so I looked into it a little bit.
Starting at 9:20pm, I started programming for 1 minute. When I started, my wakatime dashboard was showing 7 hours, 9min and ~20 sec. After 1 minute of programming, I refreshed my wakatime dashboard and it's now showing 7 hours, 11min and 23 seconds.
Just to be certain I wasn't crazy while writing this issue, I looked back at Wakatime to confirm 7 hours, 11min and 23 second, then did my 1 minute test again. After 1 minute of programming, it jumped to 7 hours, 17min and 20 sec.
Unless this is just latency in how long it takes for the wakatime dashboard to update, in which case it's totally understandable.
Update: I didn't touch Emacs at all recording the 7 hours, 11 min and 23 second. I looked at GitHub and Discord, then submitted this issue. Wakatime now shows 7 hours, 32min and 10sec...
Update 2: I haven't touched Emacs since posting this, and my time continues to go up... I think it's somehow capturing all the time I spend typing on my computer period?
The text was updated successfully, but these errors were encountered:
I believe I am also having this issue. I keep Emacs (Spacemacs) with Org mode notes in the background, while I program with other tools in the foreground. At the end of the day, WakaTime shows that Emacs has been used more than my other IDEs.
Your 1 minute tests are happening within 15 minutes of each other, so they're joined into one continuous duration. More info in keystroke timeout preference
Processing your incoming code stats isn't immediate, it happens in the background. Usually these days the delay is no more than 15-30 seconds, but back in 2020 I think it was taking longer.
Instead of looking at total time per day, look at the durations chart that shows the chunks of time you worked. That way you can time yourself working from 9:20am until 9:21am, and the chart will show that duration. Hover your mouse over the duration and the tooltip will show the exact time you started/stopped coding in that duration. So, the tooltip should say 1 min from 9:20 am until 9:21 am.
@smithandrewl yours could be a different issue, if wakatime-mode is somehow receiving cursor events when not in focus. The events should only execute when Emacs has focus and is being interacted with:
So today I noticed that my wakatime dashboard was reporting numbers much higher than I felt like they should've been, so I looked into it a little bit.
Starting at 9:20pm, I started programming for 1 minute. When I started, my wakatime dashboard was showing 7 hours, 9min and ~20 sec. After 1 minute of programming, I refreshed my wakatime dashboard and it's now showing 7 hours, 11min and 23 seconds.
Just to be certain I wasn't crazy while writing this issue, I looked back at Wakatime to confirm 7 hours, 11min and 23 second, then did my 1 minute test again. After 1 minute of programming, it jumped to 7 hours, 17min and 20 sec.
Unless this is just latency in how long it takes for the wakatime dashboard to update, in which case it's totally understandable.
Update: I didn't touch Emacs at all recording the 7 hours, 11 min and 23 second. I looked at GitHub and Discord, then submitted this issue. Wakatime now shows 7 hours, 32min and 10sec...
Update 2: I haven't touched Emacs since posting this, and my time continues to go up... I think it's somehow capturing all the time I spend typing on my computer period?
The text was updated successfully, but these errors were encountered: