uucore/parse_time: parsing a very small number takes a lot of time
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
OSS-Fuzz has found a bug in this project. Please see https://oss-fuzz.com/testcase?key=6665408282427392 for details and reproducers.
This issue is mirrored from https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=511831397 and will auto-close if the status changes there.
If you have trouble accessing this report, please file an issue at https://github.com/google/oss-fuzz/issues/new.
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 with the OSS-Fuzz testcase and reproducer linked in the issue, then trace the uucore/parse_time entry point. Confirm the excessive runtime for a very small number and inspect the surrounding parsing behavior. Done means the reproducer completes promptly without regressing the relevant parsing behavior, with a regression test if the project’s existing tests cover this path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100