wakatime-cli: Wakatime just stopped working
Expected behavior (what should have happened): Should to track activity
Actual behavior (what went wrong): My analytics are not syncing
Environment:
- OS: macOS Monterey (12.5.1)
- Platform: Intel
- IDE: VS Code
Logs:
{"caller":"cmd/run.go:270","func":"cmd.runCmd","level":"error","message":"failed to run command: today fetch failed: failed fetching today from api: failed to make request to \"https://api.wakatime.com/api/v1/users/current/statusbar/today\": Get \"https://api.wakatime.com/api/v1/users/current/statusbar/today\": EOF","now":"2022-08-26T21:48:51-03:00","version":"v1.54.0"}
{"caller":"cmd/run.go:270","func":"cmd.runCmd","level":"error","message":"failed to run command: sending heartbeat(s) later because currently rate limited: won't send heartbeat due to backoff","now":"2022-08-26T22:00:24-03:00","version":"v1.54.0"}
Wakatime always worked well on my machine, but today I saw a message on status bar wakatimeError. I generated a new API Key, disabled and uninstalled extension, installed again and now the timer always show 0 sec.
What I need to do? Thanks in advance
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (9 by maintainers)
That’s actually a different bug in the vscode plugin, which we fixed in vscode-wakatime release v19.2.0.
Upgrading your plugin in vscode will get it working again.
Hi there, sorry for late response. But now it’s working like a charm in my machine. I changed the default DNS from my internet provider to Cloudfare (1.1.1.1). I compared with my co-workers and who are using another internet provider still working. Maybe something related with default DNS of my Internet. Thanks for support!
PS: After updated to the latest version (19.1.0), sync has stopped again =/ But this time there is no log to see what’s happening
PS2: I revert my DNS to default from my internet provider and there are no errors, but sync isn’t working and there are no logs showing too