DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=tSHq
	9hnuezOfJCIEmA6gbjJR8bDOrSTX/lc1T8ffvwmAtDttVAGuAGCTUhI7BzO6N16y
	qSvMXuaePX3/l/6rus+kuG3HZZpSIC4n20Fm4iJUT2AhziiupOvaQ13tyzhqeRku
	xc/o9UcyUivgg9Af3nhSVyf9xrPk8zt+AxpqI0k=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Sat, 17 Aug 2019 11:22:55 +1000
From: Duncan Roe <duncan_roe AT optusnet DOT com DOT au>
To: cygwin AT cygwin DOT com
Subject: Re: Error "fatal: write failure on 'stdout': No error" in native console
Message-ID: <20190817012255.GB4911@dimstar.local.net>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <1114286574 DOT 20190816133658 AT yandex DOT ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1114286574.20190816133658@yandex.ru>
User-Agent: Mutt/1.10.1 (2018-07-13)

Hi Audrey,

On Fri, Aug 16, 2019 at 01:36:58PM +0300, Andrey Repin wrote:
> Greetings, All!
>
> I'm trying to resolve the problem at my new workplace, which seems to be
> affecting the ability to use git with VS Code.
> It just does not see the repo, no matter if I point its nose directly to the
> directory.
>
> When toying around the terminal, I noticed that calling simple
>
> > git log | head -1
> commit 8f4c6f50a4c6becee2c6007fdb2e67be70fc06b6
> fatal: write failure on 'stdout': No error
>
> Bummer. I can't replicate it on my home system, which have more or less
> identical setup.
> Any pointers?
>
> P.S.
> This all happens on Win7 PRO.
>
>
> --
> With best regards,
> Andrey Repin
> Friday, August 16, 2019 13:32:30
>
> Sorry for my terrible english...

Cheap & cheerful solution:

> git log | head -1 2>/dev/null

You got your 1 line of output.

The head program closes stdin after reading "n" lines. That sends SIGPIPE to the
previous process, or EPIPE to write(), if SIGPIPE is caught. I suspect you are
seeing the latter, but with errno not getting set properly for some reason.

If you would care to experiment with a simple C program that outputs a few lines
and try catching SIGPIPE you may well come up with an STC.

Cheers ... Duncan.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple