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

cmd/go: go get dropping Windows proxy settings (WSL) #38610

Closed
mcandre opened this issue Apr 23, 2020 · 4 comments
Closed

cmd/go: go get dropping Windows proxy settings (WSL) #38610

mcandre opened this issue Apr 23, 2020 · 4 comments

Comments

@mcandre
Copy link

@mcandre mcandre commented Apr 23, 2020

What version of Go are you using (go version)?

14

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

Windows Subsystem for Linux (Ubuntu)

Windows 10 64-bit

What did you do?

Ran go get for tyk dependencies.

What did you expect to see?

The dependencies install.

What did you see instead?

Network errors indicating Go in WSL was dropping the Windows host network settings.

Not sure if this is a Go thing or just a WSL thing.

@mattn
Copy link
Member

@mattn mattn commented Apr 23, 2020

You can use $http_proxy or $https_proxy on Linux.

@andybons andybons changed the title go get dropping Windows proxy settings (WSL) cmd/go: go get dropping Windows proxy settings (WSL) Apr 23, 2020
@andybons andybons added this to the Unplanned milestone Apr 23, 2020
@andybons
Copy link
Member

@andybons andybons commented Apr 23, 2020

@bcmills
Copy link
Member

@bcmills bcmills commented Apr 23, 2020

Not sure if this is a Go thing or just a WSL thing.

I think we need a firmer answer on what the WSL proxy behavior is expected to be before we can pursue this as a Go bug. (To my knowledge, nobody on the Go team is an expert on WSL usage.)

However, note that the Go porting policy requires a maintainer and builder for each supported platform. We have builders for (and do support) many Linux systems in general, but since we do not have builders or specific maintainers for WSL (#17365), to the extent that WSL differs from other Linux environments we cannot in general support it. (This is similar to the current situation for QEMU; compare #1508.)

If you require Go-on-WSL support, you should either escalate those issues to the WSL developers (presumably at Microsoft?), or volunteer (or find some one to volunteer) to set up and maintain a WSL builder environment.

@gopherbot
Copy link

@gopherbot gopherbot commented May 23, 2020

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

@gopherbot gopherbot closed this May 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.