ActivityWatch / ActivityWatch/aw-watcher-vscode

Inconsistency in tracked times

Offen
#10 7 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
TypeScript
Sterne
280
Forks
46
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

First of all, i don't know if I should post this here, or in the activitywatch repository, or in the forums.
Anyway, feel free to move the post where you think.

I have been using activity watch with vscode watcher for some time in addition to wakatime, and I have found the following inconsistencies.

Let's take today as an example.
First, in aw, the tracked (non afk) time for vscode is 52m, (1h20m total time with afk time)
![code-aw](https://user-images.githubusercontent.com/4948172/60902212-8cdeec00-a26f-11e9-8cec-6ba6053b4dd8.PNG)

Then, the time tracked by vscode-watcher is 22minutes.
From those 22minutes, the time tracked by project is the following:
![watcher](https://user-images.githubusercontent.com/4948172/60902320-b566e600-a26f-11e9-88ab-654c3bb467c4.PNG)

Now in wakatime, i know their heartbeats are more spaced than activitywatch, but their tracked time is pretty different. 1h47min in total, with this project time:
![wakatime](https://user-images.githubusercontent.com/4948172/60902452-ef37ec80-a26f-11e9-9656-3063b158575d.png)

Thanks for your time

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.