-
Notifications
You must be signed in to change notification settings - Fork 44
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
Silently failed to send my statistics for a week #95
Comments
I tried to restart my machine, and now WakaTime is endlessly |
The good thing is, as long as you don't delete your The fastest way to fix this is to install Python3 from here: Make sure to install in the default location, then WakaTime will detect and use this Python which comes with a suitable TLS CA cert for connecting to WakaTime servers. |
I have python 3 installed. I also just linked it in WakaTime settings. It finds it alright and tries to send data but |
Does it matter if I use Homebrew to install it or Python's own installer? |
Homebrew is good, sorry I thought you were on Windows not OSX. |
Python 3.6.8 |
That's the exit code corresponding to an API error, which is caused by the original error: Does this folder exist? I think when installing NextGIS it changed the default python for your system, and uninstalling broke it. What's the path of your python binary, for ex |
Nope, I deleted it. ➜ which python3
/usr/local/bin/python3 |
I just upgraded the plugin with a new version of certifi which is the library that detects the location of ca cert files for wakatime. If you upgrade wakatime for Sublime, it might start working because the new version uses a bundled |
Thank you! Meanwhile I added WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),)': /simple/certifi/ |
I upgraded plugin up to 8.3.5 but the error didn't change: OSError: Could not find a suitable TLS CA certificate bundle, invalid path: /Users/***/Applications/NextGIS/Library/Frameworks/openssl.framework/Resources/ssl/certs/cert.pem |
Just released another version with a patched certifi library that forces using local package https://github.com/wakatime/wakatime/commit/8db46bb07dc3fd9e85480c3d05911f545f435475 was the fix, because the system's certifi library must be installed in the deleted |
OK, I'll try it now. For now I installed NextGIS again (and it fixed WakaTime immediately), and then checked its installation log. Finally I know what's going on. NextGIS uses
|
Well, it works when I put a wrong URI in both |
Yes, glad it's working. Just curious, does it also work with v8.3.6 and the |
Yes, it works. But I cannot be sure what exactly solved this issue, because |
An easy way to tell is run this command: Then if |
I deleted NextGIS immediately after I installed it again (but saved its cert.pem just in case though moved it to another folder). And both Terminal and WakaTime updated silently so when I tried to update it after your letter, it was already 8.3.6. I guess, to check it properly I need to reinstall and delete version of NextGIS that I had before, and downgrade WakaTime. I could try it if you need this test. |
No that's fine, as long as it's working for you I don't want to take up more of your time. I can reproduce this on my end if needed. |
I haven't visited dashboard for a week or so. And just today I've found out that it is empty.
Statusbar shows that
WakaTime OK
. Sessions table in.wakatime.db
is empty. Thoughheartbeats
table is not.WakaTime log contains the same repeating error for week:
I can trace the reason: I deleted Next GIS just around this time. I have no idea why a certificate from the innards of Next GIS was used by WakaTime, but I guess it has something to do with the configuration of my machine.
Why WakaTime was OK all this time?
And how do I fix this?
The text was updated successfully, but these errors were encountered: