git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Problem while cloning a git repo

From
Yann COLLETTE <ycollette.nospam@free.fr>
Date
Nov 13, 2013, 07:58 UTC
Message-ID
<52833129.6060707@free.fr>
In-Reply-To
<20131113002035.GK183446@vauxhall.crustytoothpaste.net>
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 ...

Le 13/11/2013 01:20, brian m. carlson a écrit :
Show 15 quoted lines
> On Tue, Nov 12, 2013 at 01:50:24PM +0100, ycollette.nospam@free.fr wrote:
>> Hello,
>>
>> When I clone a repository, I get an error from git:
>>
>> git clone http://192.168.0.18:8080/test test_Gerrit
>> Clonage dans 'test_Gerrit'...
>> remote: Counting objects: 25106, done
>> remote: Finding sources: 100% (25106/25106)
>> error: RPC failed; result=56, HTTP code = 200iB | 8.12 MiB/s
> curl code 56 is a receive error (CURLE_RECV_ERROR).  It sounds like
> you're encountering some sort of network error or broken proxy.  Does
> cloning this repository over the git protocol or SSH work, or can you
> try it over https (to avoid the proxy)?
>
Previous: brian m. carlsonNext: brian m. carlson
Message 3 of 6 in “Problem while cloning a git repo”
  1. ycollette.nospam@free.frNov 12, 2013
  2. brian m. carlsonNov 13, 2013
  3. Yann COLLETTENov 13, 2013
  4. brian m. carlsonNov 13, 2013
  5. Yann COLLETTENov 14, 2013
  6. ycollette.nospam@free.frNov 18, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.