From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Yaron Scheffer <yscheffer@protonmail.com>
Cc: meta@public-inbox.org
Subject: Re: Corrupted lkml repo?
Date: Fri, 2 Nov 2018 20:36:58 +0000 [thread overview]
Message-ID: <20181102203658.otux6kwxsr3wh37y@dcvr> (raw)
In-Reply-To: <20181030153806.GB9025@pure.paranoia.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Tue, Oct 30, 2018 at 03:55:23AM +0000, Yaron Scheffer wrote:
> >
> > Several attempts spread over several days to git clone
> >
> > https://lore.kernel.org/lkml/0
> >
> > The process fails with the error "server hung up
> > unexpectedly", at right about the 100% mark.
> >
> > Is anyone else seeing this?
>
> You're hitting a timeout on the AWS side of things that we can't extend.
> Please clone from our mirror instead:
Konstantin: Is that time-to-first-byte, overall transfer time
or something to do with POST requests being treated differently?
Yaron: does disabling smart HTTP to rely on only GET transfers
improve things? Smart HTTP is great for bandwidth reduction but
uses more CPU/memory on the server side, and perhaps
recommending clients do that for big repos is a good thing
anyways for the initial clone.
GIT_SMART_HTTP=0 git clone --mirror ...
next prev parent reply other threads:[~2018-11-02 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 3:55 Corrupted lkml repo? Yaron Scheffer
2018-10-30 15:38 ` Konstantin Ryabitsev
2018-11-02 20:36 ` Eric Wong [this message]
2018-11-03 8:34 ` Yaron Scheffer
2018-11-04 3:50 ` Eric Wong
2018-11-05 13:20 ` Konstantin Ryabitsev
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181102203658.otux6kwxsr3wh37y@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.org \
--cc=yscheffer@protonmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).