{"thread":{"id":"56200","subject":"BUG: git log dies to SIGPIPE","startedAt":"2021-08-02T17:47:06Z","lastAt":"2021-09-27T00:30:22Z","messageCount":5,"participants":["Joseph Jenne","Jeff King","ZheNing Hu","Ævar Arnfjörð Bjarmason"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"431736","messageId":"CAB5AetcMK6=yZh4OY-0A6x6vs7X+0_1APfp4cCP_MSK_TO46ow@mail.gmail.com","threadId":"56200","inReplyTo":null,"subject":"BUG: git log dies to SIGPIPE","fromName":"Joseph Jenne","fromEmail":"joseph.jenne15@gmail.com","sentAt":"2021-08-02T17:46:53Z","receivedAt":"2021-08-02T17:47:06Z","isPatch":false,"sender":{"key":"joseph.jenne15@gmail.com","avatar":null},"body":"What did you do before the bug happened? (Steps to reproduce your issue)\nused `git log`, exiting the viewer (`less`) before reading the entire\ncommit history of the project\nWhat did you expect to happen? (Expected behavior)\nnormal exit with status code 0\nWhat happened instead? (Actual behavior)\ngit log dies to SIGPIPE after `less` exits\nWhat's different between what you expected and what actually happened?\ngit does not exit normally as would be expected\nAnything else you want to add:\n\n\n\n[System Info]\ngit version:\ngit version 2.30.2\ncpu: x86_64\nno commit associated with this build\nsizeof-long: 8\nsizeof-size_t: 8\nshell-path: /bin/sh\nuname: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-2 (2021-07-20) x86_64\ncompiler info: gnuc: 10.2\nlibc info: glibc: 2.31\n$SHELL (typically, interactive shell): /bin/zsh\n"},{"id":"431739","messageId":"YQg0t2bzqwBJ02yL@coredump.intra.peff.net","threadId":"56200","inReplyTo":"CAB5AetcMK6=yZh4OY-0A6x6vs7X+0_1APfp4cCP_MSK_TO46ow@mail.gmail.com","subject":"Re: BUG: git log dies to SIGPIPE","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2021-08-02T18:08:55Z","receivedAt":"2021-08-02T18:08:58Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Aug 02, 2021 at 10:46:53AM -0700, Joseph Jenne wrote:\n\n> What did you do before the bug happened? (Steps to reproduce your issue)\n> used `git log`, exiting the viewer (`less`) before reading the entire\n> commit history of the project\n> What did you expect to happen? (Expected behavior)\n> normal exit with status code 0\n> What happened instead? (Actual behavior)\n> git log dies to SIGPIPE after `less` exits\n> What's different between what you expected and what actually happened?\n> git does not exit normally as would be expected\n\nFWIW, there was a discussion about this a few months ago:\n\n https://lore.kernel.org/git/YAG%2FvzctP4JwSp5x@zira.vinc17.org/\n\n-Peff\n"},{"id":"431740","messageId":"CAB5Aetcr4KWpyv13DtmxxfUBwEN4fgWHgmbN7YcJ9Lgs2viAVg@mail.gmail.com","threadId":"56200","inReplyTo":"YQg0t2bzqwBJ02yL@coredump.intra.peff.net","subject":"Re: BUG: git log dies to SIGPIPE","fromName":"Joseph Jenne","fromEmail":"joseph.jenne15@gmail.com","sentAt":"2021-08-02T18:16:13Z","receivedAt":"2021-08-02T18:16:28Z","isPatch":false,"sender":{"key":"joseph.jenne15@gmail.com","avatar":null},"body":"Thanks, I'll check it out.\n\nOn Mon, Aug 2, 2021 at 11:08 AM Jeff King wrote:\n>\n> On Mon, Aug 02, 2021 at 10:46:53AM -0700, Joseph Jenne wrote:\n>\n> > What did you do before the bug happened? (Steps to reproduce your issue)\n> > used `git log`, exiting the viewer (`less`) before reading the entire\n> > commit history of the project\n> > What did you expect to happen? (Expected behavior)\n> > normal exit with status code 0\n> > What happened instead? (Actual behavior)\n> > git log dies to SIGPIPE after `less` exits\n> > What's different between what you expected and what actually happened?\n> > git does not exit normally as would be expected\n>\n> FWIW, there was a discussion about this a few months ago:\n>\n> https://lore.kernel.org/git/YAG%2FvzctP4JwSp5x@zira.vinc17.org/\n>\n> -Peff\n"},{"id":"437081","messageId":"CAOLTT8QqF-4rRiuWwntA3TfauCfc-MKingPQmyuKw3r5zf7O3A@mail.gmail.com","threadId":"56200","inReplyTo":"CAB5AetcMK6=yZh4OY-0A6x6vs7X+0_1APfp4cCP_MSK_TO46ow@mail.gmail.com","subject":"Re: BUG: git log dies to SIGPIPE","fromName":"ZheNing Hu","fromEmail":"adlternative@gmail.com","sentAt":"2021-09-26T13:17:45Z","receivedAt":"2021-09-26T13:23:49Z","isPatch":false,"sender":{"key":"adlternative@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58138461?v=4"},"body":"Joseph Jenne 于2021年8月3日周二 上午1:47写道：\n>\n> What did you do before the bug happened? (Steps to reproduce your issue)\n> used `git log`, exiting the viewer (`less`) before reading the entire\n> commit history of the project\n> What did you expect to happen? (Expected behavior)\n> normal exit with status code 0\n> What happened instead? (Actual behavior)\n> git log dies to SIGPIPE after `less` exits\n> What's different between what you expected and what actually happened?\n> git does not exit normally as would be expected\n> Anything else you want to add:\n>\n>\n>\n> [System Info]\n> git version:\n> git version 2.30.2\n> cpu: x86_64\n> no commit associated with this build\n> sizeof-long: 8\n> sizeof-size_t: 8\n> shell-path: /bin/sh\n> uname: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-2 (2021-07-20) x86_64\n> compiler info: gnuc: 10.2\n> libc info: glibc: 2.31\n> $SHELL (typically, interactive shell): /bin/zsh\n\nI may be a little unresponsive, I also saw this bug today, and there\nis no such bug\nin a small repository, it only appears in a large repository.\n\nI now know that it comes from outside git, this is really bad.\n\n--\nZheNing Hu\n"},{"id":"437099","messageId":"87y27i273e.fsf@evledraar.gmail.com","threadId":"56200","inReplyTo":"CAOLTT8QqF-4rRiuWwntA3TfauCfc-MKingPQmyuKw3r5zf7O3A@mail.gmail.com","subject":"Re: BUG: git log dies to SIGPIPE","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-09-27T00:29:32Z","receivedAt":"2021-09-27T00:30:22Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"\nOn Sun, Sep 26 2021, ZheNing Hu wrote:\n\n> Joseph Jenne 于2021年8月3日周二 上午1:47写道：\n>>\n>> What did you do before the bug happened? (Steps to reproduce your issue)\n>> used `git log`, exiting the viewer (`less`) before reading the entire\n>> commit history of the project\n>> What did you expect to happen? (Expected behavior)\n>> normal exit with status code 0\n>> What happened instead? (Actual behavior)\n>> git log dies to SIGPIPE after `less` exits\n>> What's different between what you expected and what actually happened?\n>> git does not exit normally as would be expected\n>> Anything else you want to add:\n>>\n>>\n>>\n>> [System Info]\n>> git version:\n>> git version 2.30.2\n>> cpu: x86_64\n>> no commit associated with this build\n>> sizeof-long: 8\n>> sizeof-size_t: 8\n>> shell-path: /bin/sh\n>> uname: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-2 (2021-07-20) x86_64\n>> compiler info: gnuc: 10.2\n>> libc info: glibc: 2.31\n>> $SHELL (typically, interactive shell): /bin/zsh\n>\n> I may be a little unresponsive, I also saw this bug today, and there\n> is no such bug\n> in a small repository, it only appears in a large repository.\n>\n> I now know that it comes from outside git, this is really bad.\n\nPlease see the discussion starting at\nhttps://lore.kernel.org/git/YAG%2FvzctP4JwSp5x@zira.vinc17.org/ about\nwhether this is even considered a bug, but in any case the causes are\nwell understood.\n"}]}