basenc: emit partial output on invalid input
Open
Nobody has claimed this yet.
U - basenc
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
This is a GNU behavior bug (i.e. this is a bug because GNU behaves differently, even though uutils' current behavior could be considered reasonable, too).
Example:
$ echo -n 'ze16jx(mMba' | LC_ALL=C basenc --z85 -d # GNU
missing!basenc: invalid input
[$? = 1]
$ echo -n 'ze16jx(mMba' | cargo run basenc --z85 -d # uutils
basenc: error: invalid input
[$? = 1]
I would prefer to first land #6007 before starting work on this issue.
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 basenc command entry point and reproduce the supplied --z85 -d command with the example input, comparing uutils output with GNU behavior. Trace invalid-input handling and add coverage for the expected partial output, error message, and exit status of 1.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100