From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 129366 invoked by alias); 17 Aug 2019 01:23:03 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 129330 invoked by uid 89); 17 Aug 2019 01:23:02 -0000 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 Received: from mail105.syd.optusnet.com.au (HELO mail105.syd.optusnet.com.au) (211.29.132.249) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 17 Aug 2019 01:22:59 +0000 Received: from dimstar.local.net (unknown [114.72.91.7]) by mail105.syd.optusnet.com.au (Postfix) with SMTP id E95E5361C63 for ; Sat, 17 Aug 2019 11:22:56 +1000 (AEST) Received: (qmail 31636 invoked by uid 501); 17 Aug 2019 01:22:55 -0000 Date: Sat, 17 Aug 2019 01:44:00 -0000 From: Duncan Roe To: cygwin@cygwin.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@cygwin.com References: <1114286574.20190816133658@yandex.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) X-IsSubscribed: yes X-SW-Source: 2019-08/txt/msg00242.txt.bz2 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