search

wakatime / wakatime-mode

Emacs plugin for automatic time tracking and metrics generated from your programming activity.
https://wakatime.com/emacs
267 stars 41 forks source link

error in process sentinel: WakaTime Error (104) Invalid API Key #43

Closed nitinprakash96 closed 3 years ago

nitinprakash96 commented 3 years ago

Editor: spacemacs Platform: MacOS

I'm not sure why this is happening. It was working perfectly fine the other day. But this error has been constant throught since this morning. I made sure the API key is set properly in my emacs (actually I haven't made any changes to my emacs config). Is there a way to troubleshoot this?

oiwn commented 3 years ago

same issue bot emacs (spacemacs) and (neo)vim.

There is ticket from 2018 https://github.com/wakatime/wakatime-mode/issues/38 with comment:

This was a temporary problem on our end and should be fixed now.

h-des commented 3 years ago

Neovim error:

Error detected while processing function <SNR>30_NeovimAsyncExitHandler:
line    6:
[WakaTime] Error 104: Invalid API Key
oiwn commented 3 years ago

Neovim error:

Error detected while processing function <SNR>30_NeovimAsyncExitHandler:
line    6:
[WakaTime] Error 104: Invalid API Key

yea exactly same trace.

kongds commented 3 years ago

same issue

➜ ~ /usr/local/bin/wakatime --key <api-key> --entity . ➜ ~ echo $? 104

In python source code,wakatime/api.py: send_hearbeat function return 401 with {"error":"Unauthorized"} (version 13.0.7)

kadircancetin commented 3 years ago

Same issue. I had to disable wakatime mode. I have never set thewakatime-api-key. It was writen in .wakatime.cfg file. Error is:

error in process sentinel: cond: WakaTime Error (104) Invalid API Key. Set your api key with: (custom-set-variables ’(wakatime-api-key "XXXX"))

thomasf commented 3 years ago

and it really slows emacs down a lot, the mode should disable itself or something if it fails to start.

emacsified commented 3 years ago

This issue appears to be a global issue (see below) But I am also getting this

alanhamlett commented 3 years ago

Sorry, this was me. 😭 I broke the api key parsing, but it's fixed now. The plugin saves your stats and syncs them up the next time the plugin runs (the next time you're typing) so nothing is lost, but still sorry about the frustration it may have caused.

nitinprakash96 commented 3 years ago

Sorry, this was me. 😭 I broke the api key parsing, but it's fixed now. The plugin saves your stats and syncs them up the next time the plugin runs (the next time you're typing) so nothing is lost, but still sorry about the frustration it may have caused.

Thanks a lot for fixing it @alanhamlett Cheers!