sort, uniq, fold: a read error does not say which input failed
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
Start with sort, uniq, and fold read-error handling, then inspect misc/read-errors.sh from the referenced #14705 checks. Compare the current output with the GNU examples in the issue, including multiple inputs and standard input (-). Done means each failing input is identified in the error message and the checks pass; a linked open pull request (#15191) is already working on this issue.
Written by the indexing model from the issue text.
Description
$ mkdir d
$ sort d
sort: read failed: Is a directory
$ uniq d
uniq: read error: Is a directory
$ fold d
fold: failed to read line: Is a directory
GNU 9.12 names the input, - for standard input: sort: read failed: d: Is a directory, uniq: error reading 'd': Is a directory, fold: d: Is a directory, and the same with - when the directory comes on standard input. With several inputs, uutils gives no way to tell which one failed. uutils main at a5bc606e4. Part of what misc/read-errors.sh in #14705 checks.
- 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 6 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
-
area:desktop priority:p2 type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
fritzprix/libr-agent#2165 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:ecosystem bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Chelis-Lang/chelis#3942 ·
Maintainers usually reply within 1 day