Cannot read properties of undefined (reading 'dispose') Error

[dawesi]

Plugin does not activate anymore and get this error.

VSCode 1.75.1 (system setup)

Electron 19.1.9
Chromium : 10.20.5005.194
NodeJS : 16.14.2
V8 10.2.154.23-electron.0
OS Window_NT x64 10.0.0.25281
Sandboxed : No.

[alanhamlett]

How about with the latest update today, v24.0.6?

[dawesi]

After update to v24.0.6

Runtime Status:
Activation Event:Startup
Activation Time:25ms (33ms after disable/enable)

Seems to be activated (so not showing error) but not showing in status bar even with it set to true
Not reporting to wakatime

[dawesi]

Above error is gone, so will close this an open another issue.

[alanhamlett]

Ok, one thing to check is if the wakatime commands are present in the command palette. Another thing to try is enabling debug mode with the wakatime.debug command or manually adding debug = true in your ~/.wakatime.cfg file.

With debug enabled, you will get more waka logs in your vscode dev console window. That should help us figure out whats going on and where it's failing to activate.

[dawesi]

commands work, cfg works (seems to)... but it's either not applying the config or it's weirdly broken

did all that and now no matter what version is installed the plugin is fried... #weird can't even go back to a good version it seems

I have no idea why it's not working, it was one minute, upgraded on next launch and now can't even kick it to make it work??!

Nothing in vscode logs, in developer tools console... not sure what else to do.

[dawesi]

oh wait.. latest version now working and calculating time spent today in background...

[dawesi]

turned debug on, that was last change, now working?? and syncing... #weird...

does still say 0 secs coding time for today tho... but can live with that not updating for now.

[alanhamlett]

The 0 secs will update soon, it's cached on our api side. Glad it's working! You should turn off debug mode to prevent any slowness.