-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Support downloading the language server through proxy settings #2385
Comments
Do you need a way to set proxy settings to make this work? I would assume we are already using the proxy settings of your OS so it's a question of whether being able to set more specific settings would have somehow alleviated this failure. |
Unfortunately no. Solution: All we need to do is get the proxy from the config as follows:
Note, VSC have an issue that would automate this process for us. |
@brettcannon |
Yes, it's a P0 for September, but it's a P1 for August. |
Flagging this as a good first issue since Don basically said what to do. 😁 |
I've picked up this task, and after reading into the issue a bit I see this information on the subject here: Proxy support for extensions being what it is today, plus @DonJayamanne's suggestion above, means that we will support the proxy but not any further authentication. Instead, we will wait for VSCode support for downloading extra assets during extension installation via microsoft/vscode#53855. |
Environment data
Actual behavior
Language server and linting does not work
Expected behavior
Language server and linting should work
Steps to reproduce:
Behind company proxy (I believe this is causing the issue)
Logs
Starting Microsoft Python language server.
Downloading https://pvsc.blob.core.windows.net/python-language-server/Python-Language-Server-win-x64.0.1.18204.3.nupkg... failed.
Error: tunneling socket could not be established, cause=write EPROTO 101057795:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:d:\buildagent\workspace\318698\vendor\node\deps\openssl\openssl\ssl\s23_clnt.c:827:
The text was updated successfully, but these errors were encountered: