cp --sparse=always file /dev/stdout fails while GNU succeeds
Open
Nobody has claimed this yet.
U - cp
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
$ cp --sparse=always /etc/pacman.conf /dev/stdout
cp: '/etc/pacman.conf' -> '/dev/stdout': Invalid argument
$ /home/a/bin/gnu9.11/cp --sparse=always /etc/pacman.conf /dev/stdout
# shows content of pacman.conf
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
Reproduce the failure with cp --sparse=always /etc/pacman.conf /dev/stdout and compare it with GNU cp as shown. Trace the Rust implementation of cp and its sparse-output handling, then verify that copying to /dev/stdout succeeds and emits the file contents without the Invalid argument 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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100