-
Notifications
You must be signed in to change notification settings - Fork 141
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
vsCode Enxtension Not Respecting no_ssl_verify #111
Comments
Please check if debug mode is turned on in your vscode wakatime plugin settings. To check, press Then, let's check your |
I turned on debug and bounced vsCode. |
|
Well, that's ugly. I'll upload a file instead. |
Everything looks normal in your log file. The last heartbeat was sent today at |
@alanhamlett I agree with you. Of course, it had to make a liar out of me...typical! |
What if you toggle showing/hiding the status bar in your plugin settings? |
Also, if you open the vscode console window then refresh vscode ( |
@alanhamlett Yes, I see some mention of certificate errors (line 121). |
Yes, looks like it's an SSL cert issue. Are you using a corporate proxy?
|
No, but my corp. has recently implemented SNI, so the cert chain is different than it is expecting. That’s why I was hoping it would respect the no_ssl_verify flag that is set in ~/wakatime.cfg
I’ve had to do the same with my Git config due to SNI.
… On Jul 18, 2019, at 13:27, Alan Hamlett ***@***.***> wrote:
Yes, looks like it's an SSL cert issue. Are you using a corporate proxy?
Error: unable to get local issuer certificate
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hmm, wakatime for vscode only disables cert verification when sending heartbeats. I'll update this plugin to respect Related, just browsing the source I've spotted a few unhandled promises that would cause the stuck |
Should be fixed with v2.2.0. |
Update: Post v2.2.0, I'm still getting the "WakaTime Initializing..." indicator, but I'm not seeing any errors in the log. |
@alanhamlett Just making sure you got that last notification. I think closed issues alert differently. |
Thanks for the mention, I didn't get the notification before. Do you see errors when doing the console window refresh? |
I do see mention of cert issues (line 112). I assume you were wanting me to look in the dev tools. I didn't see anything in the Output Panel. |
This error might be causing WakaTime to detect python as installed when it's actually just a placeholder binary: Does the plugin start working if you download and install Python into the default location from: |
I ran that installer, and it suggested the same path at which I have Python installed: I went ahead and ran the upgrade, though. |
Let's just manually download and extract wakatime.zip to: Make sure the file exists in this location after extracting: Then restart vscode. It should still try and fail to download wakatime-cli but it should start working after typing in a file. |
Sorry about the delay on this. I've just extracted that and have stared to play around in a file. |
@mpearon is it still happening? |
@gandarez It appears to have been resolved! I should have updated this a while back...I’m sorry! |
No worries. |
My vsCode extension is stuck in "Wakatime Initializing..." status.
I am fairly certain that this is due to a recent deep packet inspection protocol my employers have implemented.
I'm using wakatime.exe to send heartbeats from an interactive console, and that data appears to be reaching Wakatime (my evidence is that it is showing up on the console), but data from the extension does not appear to be respecting the cfg file stored in my profile.
I'm not sure where the logs for the extension actually land, or I would attach them to this case.
The text was updated successfully, but these errors were encountered: