X-Recipient:	archive-cygwin AT delorie DOT com
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=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=+172qtnrCY
	tru/J8LtPt79VNeMo=; b=TFAU/BylLCjgqcPDuVaNOnCSfwRcyu7rmawZdYkIPf
	FEfZ+ByDiRun4+hL49mrk5LwqkyYzafAObgOAc24NJnXiK6jzglH8IInIfQInuhT
	IkmkGhw2bv4eLsW1wpx+thKXrrGYjhGV8lMrzbzqRLApZF/lhOfpQnb4P7CoLVBm
	U=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=audrey, H*F:D*com.au, HX-Languages-Length:1330, cheerful
X-HELO:	mail105.syd.optusnet.com.au
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
In-Reply-To:	<1114286574.20190816133658@yandex.ru>
User-Agent:	Mutt/1.10.1 (2018-07-13)
X-IsSubscribed:	yes

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

- Raw text -