-
Notifications
You must be signed in to change notification settings - Fork 414
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
Add option to ignore all proxies #1947
Comments
@jakegt1 could you try to add the following setting:
|
I have tried this, it does not work. Same error.
I have found a solution i think works though, but i'd like you to reproduce it if poss: I created Example org.eclipse.core.net.prefs:
|
@snjeza hope that makes sense. |
Any update on this? The above fix isn't something I can really do every time as it will be reset if the workspace is cleaned up. |
I cannot get environment variable set proxies to not apply to vscode java in any way. I do not want to set a proxy, so it would be nice to have an option to force it to ignore all system proxies.
Environment
Steps To Reproduce
Current Result
!ENTRY org.eclipse.buildship.core 2 3 2021-05-14 15:16:23.920
!MESSAGE Synchronize project $SOME_PROJECT failed due to an error connecting to the Gradle build.
!STACK 0
org.gradle.tooling.GradleConnectionException: Could not install Gradle distribution from '$INTERNAL_URL/gradle/7.0.2-bin/gradle-7.0.2-bin.zip'.
Expected Result
Add feature to ignore system proxies so as nothing i do with this plugin is external
Additional Informations
I've had forms of this problem for absolutely ages. I've tried to set a proxy using system properties, which doesn't seem to work. The only way i can get this to work is by changing bashrc to not set proxies at all, restarting vscode and then running the plugin.
If there was an option to force disabling of all proxies, that would be great as then i don't have to worry about trying to configure a proxy or having to deal with the proxy working anyway.
The other option would be to have the plugin respect the no_proxy environment variable which it does not seem to do.
The text was updated successfully, but these errors were encountered: