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.

Sign up for GitHub

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

Jump to bottom

"cannot talk to GitHub" #63

Closed
shivamMg opened this issue Sep 11, 2018 · 80 comments
Closed

"cannot talk to GitHub" #63

shivamMg opened this issue Sep 11, 2018 · 80 comments

Comments

@shivamMg
Copy link

For some reason it cannot talk to GitHub. The requests time out. GH is up. Must be something between your server and GH.

screenshot_20180911_141120
@kishaningithub kishaningithub mentioned this issue Sep 11, 2018
Closed
@niemeyer
Copy link
Owner

Right, GitHub is not accepting connections from gopkg.in right now. I'm in touch with support trying to figure out why and get it sorted.

@zcx2001 zcx2001 mentioned this issue Sep 11, 2018
Closed
@niemeyer
Copy link
Owner

As a side note, if you have a good contact at GitHub for that kind of issue, please raise attention so we can get it back up ASAP. If they take too long to respond I may end up switching IP addresses for a while so they can take their time to evaluate the issue, but I'd prefer to sort it the proper way instead.

@paltanmoy paltanmoy mentioned this issue Sep 11, 2018
Merged
@sysradium
Copy link

Unfortunately no :( Maybe switching IPs is a way to go now ...

@niemeyer
Copy link
Owner

We have a hot spare at https://p3.gopkg.in/yaml.v2 ready to switch. Let's give them another moment to evaluate the issue with the domain pointing to the right location, and if it takes too long we switch.

@niemeyer
Copy link
Owner

From GitHub:

I'm speaking with our infrastructure teams and we've just updated our status while we work on this. I'll follow up with you as soon as we have an update.

@niemeyer
Copy link
Owner

Reflected in https://status.github.com/

@niemeyer
Copy link
Owner

Update from support:

We think we found the problem machine and are looking for a root cause.

Seems to be working now. Might be fixed, but given that feedback we might still see a few bumps.

@niemeyer
Copy link
Owner

And it's sorted:

We've just deployed some changes to resolve this and I can see that https://gopkg.in/mgo.v2 is now loading again. We've updated our status back to green.

Sorry for the trouble this caused you and your users. Don't hesitate to follow up if you're still seeing any problems or if you have any questions.

@natefinch natefinch mentioned this issue Sep 11, 2018
Closed
@sysradium
Copy link

@niemeyer unfortunately the problem is back

@niemeyer
Copy link
Owner

There we go again... just got in touch with them again.

@niemeyer niemeyer reopened this Sep 11, 2018
@niemeyer niemeyer mentioned this issue Sep 11, 2018
Closed
@Ads20000
Copy link

Problems have been reflected on GitHub System Status

@andrewslotin
Copy link

It looks like the same issue is happening again. I'm currently experiencing the same behaviour while trying to install the gometalinter.v2:

$ curl https://gopkg.in/alecthomas/gometalinter.v2
Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/alecthomas/gometalinter.git/info/refs?service=git-upload-pack: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

@bcmills bcmills mentioned this issue Sep 11, 2018
Closed
@niemeyer
Copy link
Owner

niemeyer commented Sep 11, 2018 •
edited
Loading

@andrewslotin Please see the last few messages above.

It also looks like it's almost sorted, from their status page:

image

@niemeyer niemeyer mentioned this issue Sep 11, 2018
Closed
@dims dims mentioned this issue Sep 11, 2018
Closed
@myitcv myitcv mentioned this issue Sep 11, 2018
Closed
@nelsam nelsam mentioned this issue Sep 11, 2018
Open
@baha-ai
Copy link

baha-ai commented Sep 11, 2018

GitHub issue still persisting
golang/go#27622 was closed but my build is still failing.

Thanks!

@sbinet sbinet mentioned this issue Sep 11, 2018
Merged
@mdittmer
Copy link

Is this a special case of this issue?

go get -u gopkg.in/src-d/go-git.v4/...                     
# cd [...]/src/gopkg.in/src-d/go-git.v4; git pull --ff-only                           
remote: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/src-d/go-git.git/info/refs?service=git-upload-pack: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
fatal: unable to access 'https://gopkg.in/src-d/go-git.v4/': The requested URL returned error: 502
package gopkg.in/src-d/go-git.v4: exit status 1
package gopkg.in/check.v1: unrecognized import path "gopkg.in/check.v1" (parse https://gopkg.in/check.v1?go-get=1: no go-import meta tags ())
package gopkg.in/src-d/go-git-fixtures.v3: unrecognized import path "gopkg.in/src-d/go-git-fixtures.v3" (parse https://gopkg.in/src-d/go-git-fixtures.v3?go-get=1: no go-import meta tags ())

@mdittmer mdittmer mentioned this issue Sep 11, 2018
Closed
@baha-ai
Copy link

baha-ai commented Sep 11, 2018

looks like it, it's a general Github http 502 error

@ucanfil
Copy link

ucanfil commented Jul 14, 2022

@hamdi-ben-yaflah mine was resolved as well.

@bhushan-mdn bhushan-mdn mentioned this issue Aug 13, 2022
Closed
@bhushan-mdn
Copy link

Guys, it's happening again. Just linking other issues so that people know what's happening.
go-yaml/yaml#887
srvaroa/labeler#43

@bhushan-mdn
Copy link

Created a discussion earlier, and based on help from @matthewgoodman13 was directed to a reddit post. Link to discussion:
https://github.com/orgs/community/discussions/29332

DasSkelett on the reddit post said that we could either use vendoring or GOPROXY. The GOPROXY route was a quick and easy fix for me. Just export the environment variable GOPROXY as proxy.golang.org and then run your go get command and you're good to go:
export GOPROXY=https://proxy.golang.org

@vitorhugods vitorhugods mentioned this issue Aug 14, 2022
Merged
4 tasks
@ishack79
Copy link

ishack79 commented Nov 2, 2022

Hi all,
I'm getting this error:

go: gopkg.in/yaml.v2@v2.2.2: unrecognized import path "gopkg.in/yaml.v2" (parse https://gopkg.in/yaml.v2?go-get=1: no go-import meta tags ())

How can be solved?

Isaac.

@EvanBoyle
Copy link

Also hitting this.

@dbizari
Copy link

dbizari commented Nov 2, 2022

Hi guys, also having this issue, anyone found any solution beside trying to use GOPROXY https://proxy.golang.org ?

@eberbis
Copy link

eberbis commented Nov 2, 2022

It seems to be resolved now 👍

@misdirectedpuffin
Copy link

misdirectedpuffin commented Nov 4, 2022 •
edited
Loading

Looks like it's happening again:

go install github.com/awslabs/amazon-ecr-credential-helper/ecr-login/cli/docker-credential-ecr-login@latest: github.com/awslabs/amazon-ecr-credential-helper/ecr-login@none updating to
        github.com/awslabs/amazon-ecr-credential-helper/ecr-login@v0.0.0-20221027043306-dc425bc05c64 requires
        github.com/stretchr/testify@v1.8.1 requires
        gopkg.in/yaml.v3@v3.0.1: 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)

Using the proxy makes no difference.

@ChenaLee
Copy link

ChenaLee commented Nov 4, 2022

Happening for me too.

@saadzaman
Copy link

Happening today again !

@metal3d
Copy link

metal3d commented Nov 4, 2022

And now…

That's a “urgent” problem while a lot of packages are referenced through gopkg.in, and we can't work on our software (build fails while getting the dependencies)

Any change to find what's the issue? (we can help on resolution)

@metal3d
Copy link

metal3d commented Nov 4, 2022 

go: fyne.io/fyne/v2@v2.2.3 requires
	gopkg.in/check.v1@v1.0.0-20200227125254-8fa46927fb4f: unrecognized import path "gopkg.in/check.v1": reading https://gopkg.in/check.v1?go-get=1: 502 Bad Gateway
	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)

@Aerowiel
Copy link

Aerowiel commented Nov 4, 2022

Yup happening for me too... with gopkg.in/square/go-jose.v2
Thanks to this issue, now i know i'm not the only facing this non-sense

@misdirectedpuffin
Copy link

Is there any workaround at all for this (other than using the proxy, which doesn't seem to work)?

@saadzaman
Copy link

saadzaman commented Nov 4, 2022 via email

@Aerowiel
Copy link

Aerowiel commented Nov 4, 2022

@saadzaman which one ?

@johnpekcan
Copy link

experiencing this as well

@johnpekcan johnpekcan mentioned this issue Nov 4, 2022
Closed
@misdirectedpuffin
Copy link

misdirectedpuffin commented Nov 4, 2022 •
edited
Loading

Adding proxy path solved the issue for meOn 4 Nov 2022 11:07 pm, Florian PENDARIES @.> wrote: Yup happening for me too... with gopkg.in/square/go-jose.v2 Thanks to this issue, now i know i'm not the only facing this non-sense —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.>

[ec2-user@ip-10-180-29-71 ~]$ GOPROXY=https://proxy.golang.org sudo /usr/bin/go install github.com/awslabs/amazon-ecr-credential-helper/ecr-login/cli/docker-credential-ecr-login@latest
go install github.com/awslabs/amazon-ecr-credential-helper/ecr-login/cli/docker-credential-ecr-login@latest: github.com/awslabs/amazon-ecr-credential-helper/ecr-login@none updating to
        github.com/awslabs/amazon-ecr-credential-helper/ecr-login@v0.0.0-20221027043306-dc425bc05c64 requires
        github.com/stretchr/testify@v1.8.1 requires
        gopkg.in/yaml.v3@v3.0.1: 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)

@saadzaman Is there another proxy I should use?

crhntr added a commit to crhntr/windows2019fs-release that referenced this issue Nov 4, 2022
@crhntr
fix: failing to clone from gopkg
391c16f 
you need to execute this after pulling a cloned repo
  git submodule sync --recursive

This should fix this issue:
	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)

It looks like it is a known issue: niemeyer/gopkg#63

So we are going around gopkg and cloneing from github directly.
@crhntr crhntr mentioned this issue Nov 4, 2022
Merged
@a-hilaly a-hilaly mentioned this issue Nov 4, 2022
Merged
@niemeyer
Copy link
Owner

niemeyer commented Nov 6, 2022

Please see #78 for details on this week's issue.

nars1 added a commit to YottaDB/YDBTest that referenced this issue Jun 2, 2023
@nars1
Set GOPROXY env var in test framework to avoid test failures when imp…
a24b7fb 
…tp randomly uses YDBGo

Background
----------
* We recently started seeing failures like the following in the YDBGo pipelines.

  ```
  # cd .; git clone -- https://gopkg.in/yaml.v3 /go/src/gopkg.in/yaml.v3
  Cloning into '/go/src/gopkg.in/yaml.v3'...
  remote: Cannot obtain refs from GitHub: cannot talk to GitHub:
    Get https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack:
    write tcp 10.131.9.188:60820->140.82.121.3:443: write: broken pipe
  fatal: unable to access 'https://gopkg.in/yaml.v3/': The requested URL returned error: 502
  package gopkg.in/yaml.v3: exit status 128
  ```

* Additionally, if I run a D_ALL in-house (where all systems share the testing workload in running
  a set of 24 E_ALLs), I used to see dozens of failures with the above symptom.

  Interestingly, rerunning those specific failing tests many times on all the systems at the same
  time did not reproduce the problem.

  So some transient network connection issue with the upstream github repository.

Issue
-----
* Found the following [solution](go-yaml/yaml#887 (comment))
  while searching online.

  _As mentioned in the [linked issue](niemeyer/gopkg#63 (comment))
  the workaround is to set environment variable GOPROXY=https://proxy.golang.org._

  _)I'm guessing this approach works as the proxy has copies of go-yaml packages cached. Once that cache
  expires however the problem will return (assuming Github continues to block gopkg.in)._

* Additionally, found the following in the [golang website](https://proxy.golang.org/).

  _proxy.golang.org - a module mirror which implements the module proxy protocol. For users downloading
  large numbers of modules (e.g. for bulk static analysis), the mirror supports a separate endpoint
  /cached-only that instructs the proxy to return only cached content. This will avoid slow downloads,
  at the cost of possibly missing some rarely-used modules._

  _GOPROXY=https://proxy.golang.org/cached-only go mod download golang.org/x/tools@v0.1.0_

Fix
---
* Therefore changed the test framework to set the `GOPROXY` env var to `https://proxy.golang.org/cached-only`
  in `com/setupgoenv.csh` at the same time `GOPATH` env var is being set. This way all tests that use go
  in the test system (all of which will go through `setupgoenv.csh`) will use the go proxy and hopefully
  not encounter these random test failures due to github connection issues.
@jacobwolfaws jacobwolfaws mentioned this issue Jun 23, 2023
Merged
@j-maltese
Copy link

@niemeyer Is the cannot talk to GitHub issue occurring again today? I'm getting a 502 when our pipelines run and "package gopkg.in/yaml.v2: exit status 128"

@j-maltese
Copy link

@niemeyer says there was a major outage this morning that is now resolved. But I am still having issues on our pipelines: https://status.canonical.com/#/incident/KNms6QK9ewuzz-7xUsPsNylV20jEt5kyKsd8A-3ptQHaFVW3sYpVjaoC6hSLL7x3PgfLD6yowK_1bYTd8bAkgg==

@jarrywangcn
Copy link

happen to me again...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests