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
Unfortunately, I can't currently use the app due to wakatime/desktop-wakatime#44. However, I dug through the code a bit and gathered a couple of hints.
Plugin user agent string is constructed in wakatime.ts#L244 with the versionString part being something like windows-wakatime/1.2.3. The user agent string then perhaps becomes something like <appName>/1.2.3 windows-wakatime/1.2.3. Wakapi uses the regex in http.go#L88 to parse that user agent string and default UA parsing as a fallback.´
Most probably, the issue lies somewhere in how we parse the user agent strings. To debug this further, however, I'd have to know exactly how the plugin constructs them and see some examples.
@Bashev, are you on Wakapi.dev? If yes, could you share your user name, please? If you're self-hosting instead, could you do me a favor and send some exemplary rows from your database's heartbeats table, that correspond to heartbeats sent by the desktop app?
muety
changed the title
Desktop App differences in data collection and processing
User agent string from desktop-wakatime parsed improperly
Oct 13, 2024
From few months wakatime has desktop app (https://github.com/wakatime/desktop-wakatime) and it seems to works with wakapi, but ... data comes with some deviations in editors section.
Desktop App partially covered support of different apps which can be tracked and is useful workaround if your tool is not supported natively yet.
Wakapi
Wakatime
Is it a data "mapping" issue or something changed on the wakatime side? Can this be applied to wakapi?
The text was updated successfully, but these errors were encountered: