bug(split): split -a 1 creates empty file before something is written to stdin
Open
Nobody has claimed this yet.
U - split
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
Hi, uutils mainteners
our testing confirmed
relunsec@relunsec:~/software/coreutils/target/debug$ ./split -a 255
split: unable to open 'xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'; aborting
relunsec@relunsec:~/software/coreutils/target/debug$
it fails in the open process after 255 and no errors reported, the gnu one not errors out
relunsec@relunsec:~/software/coreutils/target/debug$ gnusplit -a 255
and no errors
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 at the split command entry point and reproduce the reported split -a 1 behavior, then compare it with GNU split. Also run the provided split -a 255 and gnusplit -a 255 examples to clarify the expected handling of long suffixes and empty output files. Done means the Rust command matches the confirmed GNU behavior without creating an unexpected empty file or missing an error.
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
- 52/100