From: Duncan Roe <duncan_roe@optusnet.com.au>
To: cygwin@cygwin.com
Subject: Re: Error "fatal: write failure on 'stdout': No error" in native console
Date: Sat, 17 Aug 2019 01:44:00 -0000 [thread overview]
Message-ID: <20190817012255.GB4911@dimstar.local.net> (raw)
In-Reply-To: <1114286574.20190816133658@yandex.ru>
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
prev parent reply other threads:[~2019-08-17 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 11:11 Andrey Repin
2019-08-17 1:44 ` Duncan Roe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190817012255.GB4911@dimstar.local.net \
--to=duncan_roe@optusnet.com.au \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).