mv: --debug panics
Open
Nobody has claimed this yet.
U - mv
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
cargo run -p uu_mv a b --debug > /dev/full
Panics:
thread 'main' (32475) panicked at /rustc/69370dc4a8862b8401615a2a7b950704ba66c495/library/std/src/io/stdio.rs:1165:9: failed printing to stdout: No space left on device (os error 28) note: run with RUST_BACKTRACE=1environment variable to display a backtrace
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 reported cargo run -p uu_mv a b --debug > /dev/full command and observe how --debug handles the failed stdout write. Trace the uu_mv debug-output entry point, then verify that the command reports the output error without panicking when stdout has no space.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100