Skip to content
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

Closed
teucer opened this issue Aug 13, 2018 · 6 comments · Fixed by #2418
Closed

Support downloading the language server through proxy settings #2385

teucer opened this issue Aug 13, 2018 · 6 comments · Fixed by #2418
Assignees
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug good first issue important Issue identified as high-priority
Milestone

Comments

@teucer
Copy link

teucer commented Aug 13, 2018

Environment data

  • VS Code version: 1.26.0
  • Extension version (available under the Extensions sidebar): 2018.7.1
  • OS and version: windows 7
  • Python version (& distribution if applicable, e.g. Anaconda): 3.6.6 (miniconda)
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
  • Relevant/affected Python packages and their versions: XXX

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:

@brettcannon brettcannon changed the title Possible bug behind proxy? Support downloading the language server through proxy settings Aug 14, 2018
@brettcannon brettcannon added feature-request Request for new features or functionality area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. info-needed Issue requires more information from poster labels Aug 14, 2018
@brettcannon
Copy link
Member

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.

@DonJayamanne DonJayamanne added bug Issue identified by VS Code Team member as probable bug needs PR and removed info-needed Issue requires more information from poster feature-request Request for new features or functionality labels Aug 14, 2018
@DonJayamanne
Copy link

I would assume we are already using the proxy settings of your OS

Unfortunately no.

Solution: All we need to do is get the proxy from the config as follows:

proxy = workspace.getConfiguration('http').get('proxy', '');
And pass that into the request.
I missed this when reviewing the code, I've used this in the past in other extensions :(

Note, VSC have an issue that would automate this process for us.
Support downloading of additional resources when installing an extension

@DonJayamanne DonJayamanne added this to the Aug 2018 milestone Aug 14, 2018
@DonJayamanne
Copy link

@brettcannon
Changed to P0 and added to current milestone, as this has the potential to affect a number of other users.
At a minimum it'll be P0 before we switch to the language server.
Please feel free to change the labels.

@brettcannon brettcannon added important Issue identified as high-priority and removed P0 labels Aug 14, 2018
@brettcannon
Copy link
Member

Yes, it's a P0 for September, but it's a P1 for August.

@brettcannon
Copy link
Member

Flagging this as a good first issue since Don basically said what to do. 😁

@d3r3kk d3r3kk self-assigned this Aug 15, 2018
@d3r3kk
Copy link

d3r3kk commented Aug 15, 2018

I've picked up this task, and after reading into the issue a bit I see this information on the subject here:
https://code.visualstudio.com/docs/setup/network

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.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug good first issue important Issue identified as high-priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants