Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

suppress broken pipe reporting #40

Closed
sitkevij opened this issue Oct 31, 2020 · 0 comments
Closed

suppress broken pipe reporting #40

sitkevij opened this issue Oct 31, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@sitkevij
Copy link
Owner

Thanks for fixing this!

One nit: Generally unix tools don't report broken pipe errors since a tool further in the pipeline exiting without consuming all the output is normal.

See:

$ dd if=/dev/random bs=512 count=10 | xxd | head -n 1
10+0 records in
10+0 records out
5120 bytes (5.1 kB, 5.0 KiB) copied, 0.000457 s, 11.2 MB/s
00000000: fb7c 0e2c 7e8c 6cd9 da0f 74aa 86b9 2cf6  .|.,~.l...t...,.

Wheras:

$ dd if=/dev/random bs=512 count=10 | hx | head -n 1
10+0 records in
10+0 records out
5120 bytes (5.1 kB, 5.0 KiB) copied, 0.001642 s, 3.1 MB/s
0x000000: 0x02 0x3b 0x56 0x5d 0xb1 0x9a 0x6e 0xc0 0x3f 0xb0 .;V]..n.?.
error: Broken pipe (os error 32)

Originally posted by @pR0Ps in #23 (comment)

@sitkevij sitkevij added the enhancement New feature or request label Oct 31, 2020
sitkevij added a commit that referenced this issue Nov 4, 2020
#40 suppress broken pipe reporting, return 0
@sitkevij sitkevij closed this as completed Nov 9, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant