Re: Problem while cloning a git repo

2013-11-17 Thread ycollette . nospam
: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

Re: Problem while cloning a git repo

2013-11-14 Thread Yann COLLETTE
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 %).

Re: Problem while cloning a git repo

2013-11-13 Thread brian m. carlson
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

Problem while cloning a git repo

2013-11-12 Thread ycollette . nospam
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 fatal:

Re: Problem while cloning a git repo

2013-11-12 Thread brian m. carlson
On Tue, Nov 12, 2013 at 01:50:24PM +0100, ycollette.nos...@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%

Re: Problem while cloning a git repo

2013-11-12 Thread Yann COLLETTE
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