git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ycollette.nospam@free.fr
To: git@vger.kernel.org
Subject: Re: Problem while cloning a git repo
Date: Mon, 18 Nov 2013 08:31:39 +0100 (CET)	[thread overview]
Message-ID: <24843648.320766230.1384759899814.JavaMail.root@zimbra35-e6.priv.proxad.net> (raw)
In-Reply-To: <528487E3.6020503@free.fr>

When I clone a git repo from github (via https), I've no problems.
It looks like that the problem is only related to my "special" repo with big zip commited inside.

YC

----- Mail original -----
De: "Yann COLLETTE" <ycollette.nospam@free.fr>
À: git@vger.kernel.org
Envoyé: Jeudi 14 Novembre 2013 09:20:51
Objet: Re: Problem while cloning a git repo

I am not able to clone via https because gerrit doesn't propose this way 
of cloning.
When I clone via http, I see that git is starting the download of objects:
remote: Counting objects: 256, done
remote: Finding sources: 100% (256/256)
Receiving objects: 46% ... (this part always fails at 46 %).
So, I think that the proxy part is not a problem (there is no proxy set 
here).
If I set GIT_CURL_VERBOSE=1 before cloning, I've got the following error:
* Problem (2) in the Chunked-Encoded data
* Closing connection 1

YC

Le 14/11/2013 00:40, brian m. carlson a écrit :
> On Wed, Nov 13, 2013 at 08:43:28AM +0100, Yann COLLETTE wrote:
>> Hello,
>>
>> When I perform the git clone via git, it works. The problem is only
>> happening via http.
>> I tried to play with http.postBuffer and I set this parameter to
>> it's maximum (a little bit before a git clone triggered a memory
>> alloc problem) and I see that something big is trying to be
>> downloaded. But I don't see such a big file in my history of
>> commits. The maximum one seems to be around 50 Mo ...
> Please keep the list in CC.
>
> http.postBuffer doesn't affect clones, only pushes, so that isn't
> relevant here.  You're experiencing something that is dropping the
> connection over HTTP.  So you either have a bad proxy, or something else
> is causing the connection to be dropped.  Since it's only over HTTP, I
> suspect it's the former.
>
> Do you have HTTPS, and if so, does it work if you try to clone over
> that?
>


      reply	other threads:[~2013-11-18  7:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 12:50 Problem while cloning a git repo ycollette.nospam
2013-11-13  0:20 ` brian m. carlson
2013-11-13  7:58   ` Yann COLLETTE
     [not found]   ` <52832DA0.7040108@free.fr>
2013-11-13 23:40     ` brian m. carlson
2013-11-14  8:20       ` Yann COLLETTE
2013-11-18  7:31         ` ycollette.nospam [this message]

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=24843648.320766230.1384759899814.JavaMail.root@zimbra35-e6.priv.proxad.net \
    --to=ycollette.nospam@free.fr \
    --cc=git@vger.kernel.org \
    /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).