shred: a FIFO, a directory and a missing file are reported differently from GNU
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start with the shred implementation and the shred/fifo.sh test referenced in the issue. Compare how uutils handles FIFOs, directories, missing files, and sockets with the GNU output described here. Done means the relevant cases report errors matching the stated GNU behavior; an open linked pull request already exists, so check its status before starting.
Written by the indexing model from the issue text.
Description
$ mkfifo p; mkdir d
$ shred p
shred: p: Not a file
$ shred d
shred: d: Not a file
$ shred missing
shred: missing: No such file or directory
GNU 9.12 refuses a FIFO before opening it, with shred: p: invalid file type, and reports a directory or a missing file as the failure to open them: shred: d: failed to open for writing: Is a directory, shred: missing: failed to open for writing: No such file or directory. A socket gets the open failure too (failed to open for writing: Operation not supported on socket on macOS), where uutils says Not a file. uutils main at a5bc606e4. This is what shred/fifo.sh in #14705 exercises.
- Dominant language
- Rust
- Stars
- 24.3k
- Forks
- 2.1k
- Avg merge
- 2d 15m
- Merged PRs (30d)
- 320
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
-
tac: --separator rejects a value that starts with '-'Possibly taken @emirmrkaljevic claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
minorbug(mv): invalid mode errors not quotedPossibly taken @henrimarconni claimed this 3 days ago. OpenU - mv
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
ptx: break file missing path in error messagePossibly taken @Franklin-Qi claimed this 3 days ago. OpenU - ptx
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
uutils/coreutils#15307 · 1 comment ·
Maintainers usually reply within 1 day
-
minorbug(stat): os errno not stripped when failing to flush stdoutPossibly taken @cestercian claimed this 10 days ago. OpenU - stat
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
uutils/coreutils#15200 · 3 comments ·
Maintainers usually reply within 1 day
-
stty: support B460800 and B921600 baud ratesPossibly taken @oech3 claimed this 5 days ago. Openawaiting upstream U - stty
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
All issues in uutils/coreutils
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
fritzprix/libr-agent#2165 ·
Maintainers usually reply within 1 day
-
area:ecosystem bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Chelis-Lang/chelis#3942 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
review-bot
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day