pijul_org / pijul

#160 Pijul crashes when writing to a pipe that closes

Opened by porglezomp, on September 3, 2017
Closed
porglezomp commented on September 3, 2017

Example:\r +

$ pijul changes | head\r                                                                                        +
Hash: ATGbIwkct_NXCXkqeirIcojH4yF5GgWRn7pRaN6agBRxgdb41wzLkKbFG3j_R6p046VqUOchRUI9fdlajNRRfTQ\r                 +
Internal id: MZsjCRy381c\r                                                                                      +
Authors: ["Caleb Jones <code@calebjones.net>"]\r                                                                +
Timestamp: 2017-08-31 12:42:01.958614 UTC\r                                                                     +
\r                                                                                                              +
    Validate base64 argument parsing\r                                                                          +
\r                                                                                                              +
Hash: AQxZ_xO1QN21BD-y7BHEqLGhvB_iTIBoj7OrlhbM-W6tznUcuZlRbhPlxXeS-cyMINy5yFZSSxkizYxCuVZMMYg\r                 +
Internal id: DFn_E7VA3bU\r                                                                                      +
Authors: ["lthms <contact@thomasletan.fr>"]\r                                                                   +
thread 'main' panicked at 'failed printing to stdout: Broken pipe (os error 32)', src/libstd/io/stdio.rs:692:8\r+
note: Run with `RUST_BACKTRACE=1` for a backtrace.\r                                                            +
lthms commented on September 18, 2017

Looks like it has been fixed, as I can run the command you noted.

yuvallanger commented on March 24, 2019

Still happens to me:\r + \r +

$ pijul status|head\r                                                                                                      +
On branch master\r                                                                                                         +
\r                                                                                                                         +
Untracked files:\r                                                                                                         +
  (use "pijul add <file>..." to track them)\r                                                                              +
\r                                                                                                                         +
        target/wasm32-unknown-unknown/debug/.fingerprint/stdweb-e5693cae57ab8361/build\r                                   +
        target/debug/incremental/lorenz_attractor-31fsn14s89v5c/s-fan5mb4hd2-1st1o3a-38abzz3aailcm/5auujxl3r6kuzemu.o\r    +
        target/wasm32-unknown-unknown\r                                                                                    +
        target/wasm32-unknown-unknown/release/.fingerprint/rand_core-1c5c37154fe58bcd/lib-rand_core-1c5c37154fe58bcd.json\r+
        target/wasm32-unknown-unknown/debug/.fingerprint/byteorder-1ba13aa0cc2067df/invoked.timestamp\r                    +
thread 'main' panicked at 'failed printing to stdout: Broken pipe (os error 32)', src/libstd/io/stdio.rs:690:9\r           +
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.\r                                           +
```\r                                                                                                                      +
\r                                                                                                                         +
```\r                                                                                                                      +
$ pijul --version\r                                                                                                        +
pijul 0.11.1\r                                                                                                             +
$ rustc --version\r                                                                                                        +
rustc 1.33.0 (2aa4c46cf 2019-02-28)\r                                                                                      +
$ cargo --version\r                                                                                                        +
cargo 1.33.0 (f099fe94b 2019-02-12)\r                                                                                      +