Hi Max,
On Wed, 13 Feb 2019, Max Kirillov wrote:
> On Wed, Feb 13, 2019 at 10:16:26AM -0500, randall.s.becker@xxxxxxxxxx wrote:
> > On 2019-02-13, Max Kirillov, wrote:
> > As far as the unintended reuse of the output file, and issues with pipes,
> > yes, the NonStop is very sensitive to complex use of pipes and much of the
> > compatibility issues we have had relate to those (usually Linux-specific
> > pipe assumptions). That is where I have been looking when trying to debug
> > this situation (not yet found anything). This could very well be directly
> > related.
>
> You mentioned cases 6,8,13. These are all related to gipped
> request body. Could it be the git-http-backend does not
> clean a sub-process which pervforms the decompression?
That is an interesting question. From what I can see, the
`gzipped_request` flag guards a call to `inflate_request()`, which does
not explicitly close stdin, is all I could see. But it does not spawn a
sub-process from what I can see, other than the regular backend
("upload-pack" or "receive-pack").
Ciao,
Dscho
