bug(fold): when passing $'\xFF' it reports incorrect error messages
Open
Nobody has claimed this yet.
U - fold
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
Hi, uutils mainteners
the behavior of fold when passing $'\xFF' to the first arg as i see it reports invalid error messages
relunsec@relunsec:~/software/coreutils/target/debug$ ./fold $'\xFF'
fold: failed to read line: Is a directory
relunsec@relunsec:~/software/coreutils/target/debug$
while the gnu one reports the correct error message
relunsec@relunsec:~/software/coreutils/target/debug$ gnufold $'\xFF'
gnufold: ''$'\377': Invalid or incomplete multibyte or wide character
relunsec@relunsec:~/software/coreutils/target/debug$
Contributor 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.
Research direction
Start with the fold command entry point and reproduce the reported ./fold $'\xFF' behavior, comparing it with gnufold. Trace how the argument is interpreted and how the read error is produced; done means invalid or incomplete multibyte input reports the appropriate character-encoding error instead of “Is a directory”.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100