From: Jeff King <peff@peff.net>
To: "Carlos Martín Nieto" <cmn@elego.de>
Cc: Junio C Hamano <gitster@pobox.com>,
Egor Ryabkov <egor.ryabkov@gmail.com>,
git@vger.kernel.org
Subject: Re: Git fetch/pull stopped working
Date: Tue, 8 May 2012 16:18:32 -0400 [thread overview]
Message-ID: <20120508201832.GA15287@sigill.intra.peff.net> (raw)
In-Reply-To: <20120508001018.GB5067@centaur.lab.cmartin.tk>
On Tue, May 08, 2012 at 02:10:18AM +0200, Carlos Martín Nieto wrote:
> I can reproduce this issue. It happens somewhere between my phone jack
> and rackspace.
>
> I can perform 'git fetch' on other hosts and ssh -T git@github.com
> works fine. However, trying to fetch from github gives me an error.
>
> Not only this, but trying to browse to github.com or rubygems.org,
> both of which seem to be hosted on the same datacentre gives me
> timeouts or takes really long to answer. Routing traffic through my
> server in the next country over makes it work, as does fetching from
> that host.
I can't reproduce this behavior at all. Neither from rackspace's DFW
data center, nor from the IAD one (the latter is where github.com is
located).
> Yeah... It looks like the Internet is being silly. So much for routing
> around damage. What I'm not sure is how this would also affect AWS;
> maybe the Irish one?
If it was a routing issue, I wonder if it has gone away. Are you still
seeing problems?
If there's further discussion, we should probably take it off the git
list. Routing issues are definitely not a git-core problem. :)
-Peff
next prev parent reply other threads:[~2012-05-08 20:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 22:45 Git fetch/pull stopped working Egor Ryabkov
2012-05-07 23:44 ` Junio C Hamano
2012-05-08 0:10 ` Carlos Martín Nieto
2012-05-08 20:18 ` Jeff King [this message]
2012-05-08 13:59 ` Egor Ryabkov
2012-05-08 19:37 ` Junio C Hamano
2012-05-08 20:08 ` Jeff King
2012-05-08 20:29 ` Carlos Martín Nieto
2012-05-08 21:28 ` Egor Ryabkov
2012-05-11 18:47 ` Egor Ryabkov
2012-05-11 19:55 ` jaseem abid
2012-05-11 20:28 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120508201832.GA15287@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=cmn@elego.de \
--cc=egor.ryabkov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).