Re: [PATCH v8 3/3] http-backend: respect CONTENT_LENGTH for receive-pack

2018-07-25 Thread Max Kirillov
On Wed, Jul 25, 2018 at 08:41:31PM +0200, SZEDER Gábor wrote: > On Wed, Jul 25, 2018 at 4:51 PM Max Kirillov wrote: >>> I just happened to stumble upon a failure because of 'fatal: the >>> remote end hung up unexpectedly' in the test 'push plain'. >> >> Did it happen once or repeated? It is

Re: [PATCH v8 3/3] http-backend: respect CONTENT_LENGTH for receive-pack

2018-07-25 Thread SZEDER Gábor
On Wed, Jul 25, 2018 at 4:51 PM Max Kirillov wrote: > > On Wed, Jul 25, 2018 at 02:14:35PM +0200, SZEDER Gábor wrote: > >> +# sometimes there is fatal error buit the result is still 200 > >> +if grep 'fatal:' act.err > >> +then > >> +return 1 > >> +fi > > > > I just

Re: [PATCH v8 3/3] http-backend: respect CONTENT_LENGTH for receive-pack

2018-07-25 Thread Max Kirillov
On Wed, Jul 25, 2018 at 02:14:35PM +0200, SZEDER Gábor wrote: >> +# sometimes there is fatal error buit the result is still 200 > > s/buit/but/ Thanks, will fix >> +if grep 'fatal:' act.err >> +then >> +return 1 >> +fi > > I just happened to stumble upon a failure

Re: [PATCH v8 3/3] http-backend: respect CONTENT_LENGTH for receive-pack

2018-07-25 Thread SZEDER Gábor
[Hrm, this time with hopefully proper In-Reply-To: header. Sorry for the double post.] > Push passes to another commands, as described in > https://public-inbox.org/git/20171129032214.gb32...@sigill.intra.peff.net/ > > As it gets complicated to correctly track the data length, instead

Re: [PATCH v8 3/3] http-backend: respect CONTENT_LENGTH for receive-pack

2018-07-25 Thread SZEDER Gábor
> Push passes to another commands, as described in > https://public-inbox.org/git/20171129032214.gb32...@sigill.intra.peff.net/ > > As it gets complicated to correctly track the data length, instead transfer > the data through parent process and cut the pipe as the specified length is > reached.

[PATCH v8 3/3] http-backend: respect CONTENT_LENGTH for receive-pack

2018-06-10 Thread Max Kirillov
Push passes to another commands, as described in https://public-inbox.org/git/20171129032214.gb32...@sigill.intra.peff.net/ As it gets complicated to correctly track the data length, instead transfer the data through parent process and cut the pipe as the specified length is reached. Do it only