minorbug(stat): os errno not stripped when failing to flush stdout
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
Research direction
The issue identifies stat and reproduces the flush errors, but names no source file or test. Start by searching the stat implementation and existing tests for the “Error flushing stdout” message; compare the output with the linked report in issue #12901. Done means the reproduced errors no longer include the OS errno suffix, with relevant tests passing.
Written by the indexing model from the issue text.
Description
Hi, can be reproduced via both
relunsec@relunsec:~/software/coreutils/target/debug$ env --ignore-signal=PIPE ./stat . | head -n 0
Error flushing stdout: Broken pipe (os error 32)
relunsec@relunsec:~/software/coreutils/target/debug$ ./stat --format '%s' a > /dev/full
Error flushing stdout: No space left on device (os error 28)
relunsec@relunsec:~/software/coreutils/target/debug$
- Dominant language
- Rust
- Stars
- 24.2k
- Forks
- 2.1k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 331
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uutils/coreutils
-
U - mv
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
U - stat
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
ptx: break file missing path in error messagePossibly taken @ozenyunus35 claimed this 1 day ago. OpenU - ptx
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
uutils/coreutils#15307 · 1 comment ·
Maintainers usually reply within 1 day
-
stty: support B460800 and B921600 baud ratesPossibly taken @oech3 claimed this 2 days ago. Openawaiting upstream U - stty
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
B - high priority U - du
Difficulty 1/5 Under an hour Newbie friendliness 82/100
uutils/coreutils#14984 · 1 comment ·
Maintainers usually reply within 1 day
All issues in uutils/coreutils
Similar issues
-
Four problem loader browser tests fail on WindowsPossibly taken @Patriciaath999 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
starkware-libs/sequencer#15229 ·
Maintainers usually reply within 1 day
-
`fnox set` ignores piped stdin when `--description` is given, saving the secret without a valueOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
ActivityWatch/aw-notify-rs#47 · 1 comment ·