timeout: words after DURATION are still parsed as options
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 20/100
Research direction
The issue identifies the timeout command and provides reproducing invocations, but names no source file or test. Read the timeout implementation and its existing tests, then compare behavior for coreutils timeout 5 -s KILL true and coreutils timeout 5 -X. Done means arguments after DURATION are treated as the command and the resulting behavior matches GNU; a linked pull request is already open.
Written by the indexing model from the issue text.
Description
GNU treats the word after DURATION as COMMAND, even when it begins with -. uutils continues parsing options there.
Here, coreutils is the uutils multicall binary built with --features unix.
$ coreutils timeout 5 -s KILL true
uutils parses -s KILL, runs true, and exits 0. GNU tries to run a command named -s and exits 127. Likewise, timeout 5 -X is an option error with status 125 in uutils, but a missing command with status 127 in GNU.
I have a fix ready and will open the PR soon.
- 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 2 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 2 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 9 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
-
documentation P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug good first issue priority:high
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Konfirm-xyz/konfirm-contracts#163 ·
Maintainers usually reply within 1 day
-
area:gc-repack-output bug factory:dogfood factory:triaged priority:p3 type:bug type:ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gitbutlerapp/grit#1161 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
feature performance
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
lance-format/lance#10137 ·
Maintainers usually reply within 2 days