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

Wakatime not recording stats with latest vscode update. #155

Closed
nohupped opened this issue Aug 24, 2020 · 7 comments
Closed

Wakatime not recording stats with latest vscode update. #155

nohupped opened this issue Aug 24, 2020 · 7 comments

Comments

@nohupped
Copy link

Hello,
I've been using wakatime for a long time, but since the last update of vscode, it appears to stop working.

Initially, on the statusbar, it was stuck at
wakatime_initialisingpng forever.

I tried re-initializing it by deleting everything

rm -rf ~/.wakatime*

and reinstalling the plugin.

This time, it initialized, but the stats are not recording in the dashboard.

These are the errors that I see in my vscode Developer Console.

zip_header

initialized

Downloading wakatime-cli standalone...

happens every time I open the vscode.

Attaching the details of my Vscode/plugin/OS version

Version: 1.48.1
Commit: 3dd905126b34dcd4de81fa624eb3a8cbe7485f13
Date: 2020-08-19T17:11:59.963Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.8.3-arch1-1

Wakatime installed plugin version: latest at the time of reporting this.

v4.0.3

Please let me know if I am missing anything.

Thank you very much.

@alanhamlett
Copy link
Member

After uninstalling you should run rm -r ~/.vscode/extensions/wakatime* since ~/.wakatime* is your config and offline heartbeats db which shouldn't be deleted in case there were heartbeats still waiting to sync up to the api. The wakatime-cli dependency is extracted into ~/.vscode/extensions/wakatime* so removing that folder resets the plugin.

Is this bug fixed if you install the old version 4.0.0?
Screen Shot 2020-08-23 at 6 44 29 PM

@jeffryang24
Copy link

After uninstalled it and run rm -r ~/.vscode/extensions/wakatime*, still have the above error. Especially these lines still appear:

  • [WakaTime][ERROR] Error: Invalid or unsupported zip format. No END header found
  • [WakaTime][WARN] Error: ENOENT: no such file or directory, chmod '/home/jeffryangtoni/.vscode/extensions/wakatime.vscode-wakatime-4.0.3/wakatime-cli/wakatime-cli'

🙇

@alanhamlett
Copy link
Member

How about when installing the older version 4.0.0?

@alanhamlett
Copy link
Member

Fixed with v4.0.4 by reverting back to request library.

@nohupped
Copy link
Author

Thank you very much @alanhamlett. I checked it again by installing the older version 4.0.0 and it is working perfectly, however, the latest version (v4.0.5) is stuck at

wakatime_initialisingpng

since around last 20 minutes, and there is no error or warning in the Debug console on vscode.
I've tried removing the extension completely by rm -r ~/.vscode/extensions/wakatime* and started fresh but it is still stuck there in the statusbar.

Is there anything else that I am missing?

Thank you

@jeffryang24
Copy link

Yes, still stuck at WakaTime initializing in v4.0.5... 👍

@nohupped
Copy link
Author

nohupped commented Aug 24, 2020

Thank you very much @alanhamlett for fixing this in v4.0.6 and @jeffryang24 for helping.

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

No branches or pull requests

3 participants