bug(numfmt): some numbers cause incorrect conversion and logic issues
Open
Nobody has claimed this yet.
U - numfmt
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
Hi, uutils maintenenres
we tested some numbers after we reached
relunsec@relunsec:~/software/coreutils/target/debug$ ./numfmt 1091611621123456668921298.1279298262626672676226672772762626627828
1091611621123456602472448.0000000000000000000000000000000000000000
as i see the number i see looks like corrupted, i do'nt known where comes the weird behavior while gnu numfmt not produce anything
invalid, in constract it rejected it
relunsec@relunsec:~/software/coreutils/target/debug$ gnunumfmt 1091611621123456668921298.1279298262626672676226672772762626627828
gnunumfmt: value too large to be converted: ‘1091611621123456668921298.1279298262626672676226672772762626627828’
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 report with the provided oversized decimal input using the built ./numfmt command, then compare its output with gnunumfmt. Trace the numfmt conversion path responsible for accepting and changing the value; done means the input is handled without corrupted output and matches the intended rejection behavior shown by GNU numfmt.
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