wrong param parse on build duration
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
Research direction
Start at _handle_build_duration, where normal query parameters are parsed, and reproduce the issue with a duration such as 1234. Verify that max/min filtering uses the complete parameter value rather than only its first character, then retest the affected filter behavior.
Written by the indexing model from the issue text.
Description
Build duration max/min is wrong for normal query params: _handle_build_duration does value[0] on a string, so only the first digit of the string is considered. For instance, '1234' becomes '1', which causes the filter to behave improperly.
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 12
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.
More from kernelci/dashboard
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
URGENT
-
notifications
Difficulty 4/5 3-5 days Newbie friendliness 64/100
-
notifications
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
notifications
Difficulty 4/5 3-5 days Newbie friendliness 55/100
All issues in kernelci/dashboard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100