Netdev List
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Song Liu <songliubraving@fb.com>, Networking <netdev@vger.kernel.org>
Cc: Alexei Starovoitov <ast@fb.com>
Subject: Re: Failed to clone net-next.git
Date: Tue, 8 May 2018 14:06:32 -0400	[thread overview]
Message-ID: <f5d5d5c3-3b15-ddbe-45c6-9f360f1042bf@linuxfoundation.org> (raw)
In-Reply-To: <FB252D9C-2FB2-437C-8646-4F61406AC96D@fb.com>


[-- Attachment #1.1: Type: text/plain, Size: 878 bytes --]

On 05/08/18 13:46, Song Liu wrote:
> We are seeing the following error on multiple different systems while 
> cloning net-next tree. 
> 
>   $ git clone https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
>   Cloning into 'net-next'...
>   remote: Counting objects: 6017287, done.
>   remote: Compressing objects: 100% (2458/2458), done.
>   fatal: The remote end hung up unexpectedly 1.00 GiB | 8.13 MiB/s
>   fatal: early EOF
>   fatal: index-pack failed
> 
> It looks like the size of the data being fetched reached server side
> limit of 1.00 GiB. So we probably need change server side configuration.
> Could someone please look into it?

It was probably due to a timeout value. Can you try it now, I've bumped
it to a much larger number.

Regards,
-- 
Konstantin Ryabitsev
Director, IT Infrastructure Security
The Linux Foundation


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2018-05-08 18:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 17:46 Failed to clone net-next.git Song Liu
2018-05-08 18:06 ` Konstantin Ryabitsev [this message]
2018-05-08 18:37   ` Song Liu
2018-05-09  0:04 ` David Miller
2018-05-09  7:09   ` Michal Kubecek

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=f5d5d5c3-3b15-ddbe-45c6-9f360f1042bf@linuxfoundation.org \
    --to=konstantin@linuxfoundation.org \
    --cc=ast@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.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