I think `head` tends to cause SIGPIPE in practice, and that is what sigpipe_status_ok is for
but I stopped using pipefail since the return value can be based on a race, causing things to randomly not work at some point in the future.
Hm I'd be interested in an example of this
The order that processes in a pipeline finish is non-deterministic, but that should NOT affect the status, with either pipefail or not.
That is, the status should be deterministic ... it's possible that SIGPIPE is an exception to that, though that wouldn't affect YSH.
I think `head` tends to cause SIGPIPE in practice, and that is what sigpipe_status_ok is for
but I stopped using pipefail since the return value can be based on a race, causing things to randomly not work at some point in the future.
Hm I'd be interested in an example of this
The order that processes in a pipeline finish is non-deterministic, but that should NOT affect the status, with either pipefail or not.
That is, the status should be deterministic ... it's possible that SIGPIPE is an exception to that, though that wouldn't affect YSH.