gopkg
gopkg copied to clipboard
Cannot talk to GitHub
Hey, could you please take a look at this issue? Looks like its not just for the YAML packages.
https://github.com/go-yaml/yaml/issues/887
We're experiencing the same issue here https://prow.ack.aws.dev/view/s3/ack-prow-logs/pr-logs/pull/aws-controllers-k8s_rds-controller/109/rds-unit-test/1558538624394334208
I see same issue:
go: gopkg.in/[email protected]: unrecognized import path "gopkg.in/check.v1" (parse https://gopkg.in/check.v1?go-get=1: no go-import meta tags ())
go: gopkg.in/[email protected]: unrecognized import path "gopkg.in/yaml.v2" (parse https://gopkg.in/yaml.v2?go-get=1: no go-import meta tags ())
same issue here:
[gopkg.in/[email protected]:](http://gopkg.in/[email protected]) unrecognized import path "[gopkg.in/yaml.v3](http://gopkg.in/yaml.v3)": reading [https://gopkg.in/yaml.v3?go-get=1:](https://gopkg.in/yaml.v3?go-get=1) 502 Bad Gateway
server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get [https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack:](https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack) net/http: request canceled (Client.Timeout exceeded while awaiting headers)
The command '/bin/sh -c go mod download' returned a non-zero code: 1
I'm also facing same issue.
package gopkg.in/gorp.v2: unrecognized import path "gopkg.in/gorp.v2": reading https://gopkg.in/gorp.v2?go-get=1: 502 Bad Gateway
server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-gorp/gorp.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
I am having the same issue right now. Any hints about how this issue was solved back in the time?
I am having the same issue right now. I think the problem is related to Github but the status is showing all Operational https://stackoverflow.com/questions/74290916/cannot-obtain-refs-from-github-github-down-status-not-showing-any-issues
Also hitting this
And the problems is repeated fro days now... impossible to work on my apps.
A “replace” directive didn't work for me... That's a very serious problem.
Maybe I can make it work on local machine and change /etc/hosts
to fake the server...
Having this same issue for multiple days
/go/pkg/mod/github.com/spf13/[email protected]/internal/encoding/ini/codec.go:9:2: unrecognized import path "gopkg.in/ini.v1": reading https://gopkg.in/ini.v1?go-get=1: 502 Bad Gateway
server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-ini/ini.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
/go/pkg/mod/github.com/spf13/[email protected]/internal/encoding/yaml/yaml3.go:6:8: unrecognized import path "gopkg.in/yaml.v3": reading https://gopkg.in/yaml.v3?go-get=1: 502 Bad Gateway
server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
lots of comments in https://github.com/niemeyer/gopkg/issues/63 as well
I managed some things by forking repo and changed references to not use gopkg.in - but here, with Fyne.io, there are too many problems to solve.
Really, the gopkg.in idea is good, but if the service doesn't respond, that a SPOF for thouthands of projects.
Really, the gopkg.in idea is good, but if the service doesn't respond, that a SPOF for thouthands of projects.
Totally agree. I wonder if it's feasible to backup these repos/versions on a gitea or a CDN and failover to it. This just ate up my afternoon debugging why the go install
s were failing at different points trying to resolve deps while GitHub was having issues (again).
This is a critical problem i wasn't able to deploy my workload for hours. But i think the problem is related to the way this tool communicates with github. Its weird we don't hear anything from the developers. We real need to find a work around for this.
I've been off for two weeks now on intense company wide events that happen twice a year, and we still have the Ubuntu Summit starting tomorrow. That's why you haven't heard from me. That said, it's for exactly this kind of reason that this service is under the supervision of a 24x7 team at Canonical, and not me personally. I'll reach out to them.
Here is some info from the team:
We’ve had some issues one of our transit providers affecting gopkg and a number of other services. We’ve weighted/prepended them out for now so traffic is going via our other providers links.
@niemeyer , I am seeing this issue again now. Pls let me know if you a new issue needs to be created for this one.
Indeed, there was an issue today:
https://status.canonical.com/
And again it was an infrastructure-wide issue, so probably the same link misbehaving again. 😕
@niemeyer Getting the same issue again
go: gopkg.in/natefinch/[email protected]: unrecognized import path "gopkg.in/natefinch/lumberjack.v2": https fetch: Get "https://gopkg.in/natefinch/lumberjack.v2?go-get=1": dial tcp 185.125.188.113:443: i/o timeout
just saw this today:
go: gopkg.in/DataDog/[email protected]: unrecognized import path "gopkg.in/DataDog/dd-trace-go.v1": reading https://gopkg.in/DataDog/dd-trace-go.v1?go-get=1: 502 Bad Gateway
server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/DataDog/dd-trace-go.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
@niemeyer this is happening again today:
/.go/pkg/mod/github.com/spf13/[email protected]/internal/encoding/ini/codec.go:9:2: unrecognized import path "gopkg.in/ini.v1": reading https://gopkg.in/ini.v1?go-get=1: 502 Bad Gateway
server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-ini/ini.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
/.go/pkg/mod/github.com/spf13/[email protected]/internal/encoding/yaml/yaml3.go:6:8: unrecognized import path "gopkg.in/yaml.v3": reading https://gopkg.in/yaml.v3?go-get=1: 502 Bad Gateway
server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Yup I see the same thing:
remote: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
fatal: unable to access 'https://gopkg.in/yaml.v3/': The requested URL returned error: 502
EDIT:
It's fixed for me now
Seeing the same right now, not fixed yet.
Same thing for me as well.
Sorry for the trouble. I'm in touch with our IS team and apparently it's a connectivity issue again. If that's confirmed, I've suggested moving the service out of this provider to give gopkg.in a break as this is getting shameful. 😕
anyone still seeing the issue? I still get server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-check/check.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
@niemeyer When would this be resolved in your opinion. Not pushing you but rather need to inform my teammates. Thanks
So, is there any option to get around gopkg.in?
I had a successful build, if it gives anyone hope.
Think this might be here again. Am I the only one?