dircolors: directory operand exits 2 with a custom message, GNU prints 'read error: Is a directory' and exits 1
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
Research direction
The bug is in how the uutils dircolors binary handles a directory passed as the database operand: it prints expected file, got directory 'dd' and exits 2. Find where that message and exit code are produced, and change it to match GNU's read error: Is a directory with exit status 1. Done when dircolors -b <dir> prints the GNU-style message and echo $? gives 1.
Written by the indexing model from the issue text.
Description
When the database operand is a directory, uutils dircolors uses its own message and exits with 2. GNU dircolors 9.12 prints a read error and exits with 1.
$ mkdir dd
$ dircolors -b dd # GNU 9.12
dircolors: dd: read error: Is a directory
$ echo $?
1
$ coreutils dircolors -b dd # uutils main
dircolors: expected file, got directory 'dd'
$ echo $?
2
Scripts that check for exit status 1 on a bad database file see a different code. Found with behave, a black-box differential testing tool I'm building, while running a dircolors spec recorded from GNU 9.12.
- Dominant language
- Rust
- Stars
- 24.4k
- Forks
- 2.2k
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 434
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
U - shred
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
chown -v: `+ID` spec echoed verbatim on a broken symlinkPossibly taken @sunsss123soldier claimed this 1 day ago. Opengood first issue oss-scanner U - chown
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
dircolors: --csh doesn't escape `!`Possibly taken @majidninja claimed this 2 days ago. Opengood first issue oss-scanner U - dircolors
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
uutils/coreutils#16496 · 1 comment ·
Maintainers usually reply within 1 day
-
test_hostid.rs lacks test cases with frozen ip addr e.g. unshare -ru sh -c "hostname 127.0.0.1 && hostid"Possibly taken @costajohnt claimed this 3 days ago. OpenU - hostid
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
All issues in uutils/coreutils
Similar issues
-
ai_p2
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ClickHouse/ClickHouse#132519 ·
Maintainers usually reply within 1 day
-
Pattern-clip compiler tests miss the clip cap, sort order, muted output and count/emit agreementOpenarea: engine type: test
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
YuriiMurha/grooviq#224 ·
Maintainers usually reply within 1 day
-
state:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
zed-industries/zed#67109 · 1 comment ·
Maintainers usually reply within 1 day
-
bug priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
storytold/photocraft#15500 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day