sort: an invalid --parallel value is reported by clap, not as GNU does
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
Start with the sort option parsing and the checks in sort/sort.pl mentioned in the issue, then compare the listed inputs with GNU 9.12 behavior. The open linked pull request #15184 means work is already under way; check its status before attempting changes. Done means invalid values produce the described GNU-style errors and exit status 2, while --parallel=+2 is accepted.
Written by the indexing model from the issue text.
Description
$ sort --parallel=0 f
error: invalid value '0' for '--parallel <NUM_THREADS>': 0 is not in 1..18446744073709551615
$ sort --parallel=x f
error: invalid value 'x' for '--parallel <NUM_THREADS>': invalid digit found in string
$ sort --parallel=1x f
error: invalid value '1x' for '--parallel <NUM_THREADS>': invalid digit found in string
GNU 9.12 says sort: number in parallel must be nonzero, sort: invalid --parallel argument 'x' (also for -1 and an empty value) and sort: invalid suffix in --parallel argument '1x', with exit status 2, and accepts a leading + (--parallel=+2). uutils main at a5bc606e4. Part of what sort/sort.pl in #14705 checks.
- Dominant language
- Rust
- Stars
- 24.3k
- Forks
- 2.1k
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 313
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
-
fmt -p: an unprefixed last line without a newline gets one addedPossibly taken @fixfon claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
numfmt: a tab between fields is kept, GNU prints a spacePossibly taken @fixfon 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 5 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 5 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 12 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
All issues in uutils/coreutils
Similar issues
-
proxy: include denial_category in the "proxy request denied" log linePossibly taken @sreyas-endor claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
nolabs-ai/nono#2172 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
metasequoiaime/msime#9113 ·
Maintainers usually reply within 1 day
-
area:desktop priority:p2 type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area: supply-chain
Difficulty 1/5 Under an hour Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100