Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time active vs Summary Graph: Totals do not match #722

Open
2 tasks done
henry2man opened this issue Mar 16, 2022 · 7 comments
Open
2 tasks done

Time active vs Summary Graph: Totals do not match #722

henry2man opened this issue Mar 16, 2022 · 7 comments

Comments

@henry2man
Copy link

henry2man commented Mar 16, 2022

  • I am on the latest ActivityWatch version.
  • 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

  1. Open AW
  2. Read Time active time
  3. Go to the summary bar graph
  4. Go over current day/week/month (displayed in yellow)
  5. A tooltip is shown with total time.
  6. Error: Times do not match

Expected behavior

I was wondering to have the same times in both places.

Documentation

Some examples (0.11.0):

Captura de Pantalla 2022-03-16 a las 7 19 29

Captura de Pantalla 2022-03-16 a las 7 20 31

With BETA 0.12.0 - beta 1:

Captura de Pantalla 2022-03-16 a las 10 26 04

Additional context

N/A

@github-actions
Copy link

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! 🙏

@ErikBjare
Copy link
Member

ErikBjare commented Mar 16, 2022

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%.

@henry2man
Copy link
Author

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:

Captura de Pantalla 2022-03-16 a las 10 26 04

@henry2man
Copy link
Author

henry2man commented Mar 16, 2022

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.

@henry2man
Copy link
Author

henry2man commented Mar 17, 2022

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)

Captura de Pantalla 2022-03-17 a las 7 01 26

@ArthurusDent
Copy link

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

@henry2man
Copy link
Author

henry2man commented Sep 21, 2022

This is still present on newest 0.12.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants