Time active vs Summary Graph: Totals do not match
- [x] I am on the latest ActivityWatch version.
- [x] I have searched the issues of this repo and believe that this is not a duplicate.
Current setup:
- OS name and version: MacOS Monterrey 12.3
- ActivityWatch version: Version: v0.11.0 and BETA v0.12.0 beta 1 and 0.12.0
Describe the bug
Time active vs Summary Graph: Totals do not match.
To Reproduce
- Open AW
- Read Time active time
- Go to the summary bar graph
- Go over current day/week/month (displayed in yellow)
- A tooltip is shown with total time.
- Error: Times do not match
Expected behavior
I was wondering to have the same times in both places.
Documentation
Some examples (0.11.0):
With BETA 0.12.0 - beta 1:
Additional context
N/A
Hi there! As you're new to this repo, please make sure you've used an appropriate issue template and searched for duplicates (it helps us focus on actual development!). We'd also like to suggest that you read our contribution guidelines and our code of conduct. Thanks a bunch for opening your first issue! 🙏
Could you try the latest beta release and see if the issue is still there? https://github.com/ActivityWatch/activitywatch/releases/tag/v0.12.0b1
When I test it, my times also differ, but only by ~5%.
Could you try the latest beta release and see if the issue is still there https://github.com/ActivityWatch/activitywatch/releases/tag/v0.12.0b1
Unfortunately it seems that the problem is still there:
I could help with the investigation of the problem by looking at the raw data. Is there any utility to do it?
EDIT: I've just found it... but I'm a little bit overwhelmed with the syntax. Could you provide me an example to start with?
EDIT 2: I've manually aggregated aw-watcher-afk_<machinename> bucket assuming that this meter is the one that indicates exactly the time that the equipment is turned on and active (is it so?). The results are clear: the correct value is the one that it's showed in the graph.
This is crucial for me because I'm using AW as project time tracker and measured time is directly translated into customer billing.
I've checked server logs and I'm also experiencing errors like:
Gap was of negative duration but could be safely merged
...
Gap was of negative duration and could NOT be safely merged
also reported in #626 and #602, so could this be the cause of having different times on both meters?
@ErikBjare Also I've rollback the update to 0.12.0-beta1 because, for an unknown reason, AW stopped to properly show events in the dashboard (going back to 0.11.0 solves the issue)
This is still present in v0.12.0b2. "Time active" seems to be the correct total.
No problems with data visualization in "Timeline (barchart)".
System: Windows 10 21H2
This is still present on newest 0.12.0