From: "Ævar Arnfjörð Bjarmason" <avarab@gmail•com>
To: ZheNing Hu <adlternative@gmail•com>
Cc: Joseph Jenne <joseph.jenne15@gmail•com>,
Git List <git@vger•kernel.org>, Jeff King <peff@peff•net>
Subject: Re: BUG: git log dies to SIGPIPE
Date: Mon, 27 Sep 2021 02:29:32 +0200 [thread overview]
Message-ID: <87y27i273e.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <CAOLTT8QqF-4rRiuWwntA3TfauCfc-MKingPQmyuKw3r5zf7O3A@mail.gmail.com>
On Sun, Sep 26 2021, ZheNing Hu wrote:
> Joseph Jenne <joseph.jenne15@gmail•com> 于2021年8月3日周二 上午1:47写道：
>>
>> What did you do before the bug happened? (Steps to reproduce your issue)
>> used `git log`, exiting the viewer (`less`) before reading the entire
>> commit history of the project
>> What did you expect to happen? (Expected behavior)
>> normal exit with status code 0
>> What happened instead? (Actual behavior)
>> git log dies to SIGPIPE after `less` exits
>> What's different between what you expected and what actually happened?
>> git does not exit normally as would be expected
>> Anything else you want to add:
>>
>>
>>
>> [System Info]
>> git version:
>> git version 2.30.2
>> cpu: x86_64
>> no commit associated with this build
>> sizeof-long: 8
>> sizeof-size_t: 8
>> shell-path: /bin/sh
>> uname: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-2 (2021-07-20) x86_64
>> compiler info: gnuc: 10.2
>> libc info: glibc: 2.31
>> $SHELL (typically, interactive shell): /bin/zsh
>
> I may be a little unresponsive, I also saw this bug today, and there
> is no such bug
> in a small repository, it only appears in a large repository.
>
> I now know that it comes from outside git, this is really bad.
Please see the discussion starting at
https://lore.kernel.org/git/YAG%2FvzctP4JwSp5x@zira.vinc17.org/ about
whether this is even considered a bug, but in any case the causes are
well understood.
prev parent reply other threads:[~2021-09-27 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 17:46 BUG: git log dies to SIGPIPE Joseph Jenne
2021-08-02 18:08 ` Jeff King
2021-08-02 18:16 ` Joseph Jenne
2021-09-26 13:17 ` ZheNing Hu
2021-09-27 0:29 ` Ævar Arnfjörð Bjarmason [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=87y27i273e.fsf@evledraar.gmail.com \
--to=avarab@gmail$(echo .)com \
--cc=adlternative@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=joseph.jenne15@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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