-
Notifications
You must be signed in to change notification settings - Fork 57
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
Installing github.com/ramya-rao-a/go-outline FAILED #5
Comments
go get -v github.com/ramya-rao-a/go-outline Fetching https://golang.org/x/tools/go/buildutil?go-get=1 |
@zzsme Are you behind a firewall or are you using a low version of go? |
go get -u github.com/ramya-rao-a/go-outline |
I get the same here Installing github.com/ramya-rao-a/go-outline FAILED 1 tools failed to install. go-outline: |
I am seeing the same issue in our enterprise environment. We aren't able to configure proxy or direct firewall rules, but we have configured the Is there a way to update this repo to respect those variables?
|
Installing github.com/ramya-rao-a/go-outline FAILED
1 tools failed to install.
go-outline:
Error: Command failed: /usr/local/bin/go get -u -v github.com/ramya-rao-a/go-outline
github.com/ramya-rao-a/go-outline (download)
Fetching https://golang.org/x/tools/go/buildutil?go-get=1
https fetch failed: Get https://golang.org/x/tools/go/buildutil?go-get=1: dial tcp 216.239.37.1:443: i/o timeout
package golang.org/x/tools/go/buildutil: unrecognized import path "golang.org/x/tools/go/buildutil" (https fetch: Get https://golang.org/x/tools/go/buildutil?go-get=1: dial tcp 216.239.37.1:443: i/o timeout)
github.com/ramya-rao-a/go-outline (download)
Fetching https://golang.org/x/tools/go/buildutil?go-get=1
https fetch failed: Get https://golang.org/x/tools/go/buildutil?go-get=1: dial tcp 216.239.37.1:443: i/o timeout
package golang.org/x/tools/go/buildutil: unrecognized import path "golang.org/x/tools/go/buildutil" (https fetch: Get https://golang.org/x/tools/go/buildutil?go-get=1: dial tcp 216.239.37.1:443: i/o timeout)
The text was updated successfully, but these errors were encountered: