Unknown error after last upgrade
See original GitHub issueAfter the last upgrade, the plugin no longer works and on startup I get
[wakatime.js:621] Error: Command failed:
C:\Users\user\.wakatime\wakatime-cli-windows-amd64.exe --entity
C:\Users\user\Desktop\foo\bar.tex --plugin atom-wakatime/11.0.4
--write --lineno 113 --verbose --config
C:\Users\user\.wakatime.cfg --alternate-project project
I checked and proc.exitCode
is 1
. stderr
and stdout
are empty. In .wakatime.cfg
cli_version = v1.7.4
However, if I change cli_version
to v1.7.1
in .wakatime.cfg
, everything works fine.
And cli v1.7.4
is re-downloaded on every startup while v1.7.1
just prints that it’s up to date
.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
iOS update and restore errors - Apple Support
iOS update and restore errors · Try these steps first · Choose your error number or message · Update the software on your...
Read more >Unknown Error on upgrade - Microsoft Community
1. Run Windows Upgrade Advisor to see if there are any known issues that might affect the installation and fix them. · 2....
Read more >The iPhone (or iPad) Could Not Be Updated, And Unknown ...
The iPhone (or iPad) Could Not Be Updated, And Unknown Error Occurred (4000), Fix · 1. Basic steps. Please first try the following...
Read more >iOS 15 iPhone Could Not be Restored. An Unknown Error ...
Having problems restoring or updating your iPhone with iTunes ? This video shows you how to complete the restore with some simple tips, ......
Read more >Camera and related Apps not working "Unknown Error" after ...
I just upgraded my OnePlus 3 to the latest software upgrade - OnePlus A3003_16_171116. This upgraded my phone to Android O along with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
sorry for the late response but that worked thanks
@BestSithInEU @OreoDivision if you remove
no_ssl_verify = true
from~/.wakatime.cfg
then restart Atom to get the latest wakatime-cli v1.18.9, does that also fix the issue for you?