fix: week error in fuzzing scripts #4897
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue:
In bash, when you use
((
for arithmetic evaluation, numbers with leading zeros are interpreted as octal numbers. Since '9' isn't a valid octal digit, you get the error: value too great for base (error token is "09").Fix:
This PR updates the script to force decimal interpretation of the week number using 10# in the arithmetic expression:
at_index=$(((10#$(date -u +%U)) % ${#fuzzing_scripts[@]}))
As you can see now, the correct script is being selected for week 9. I've also tested running fuzzing script on my fork in GitHub Actions.
https://github.com/its403/cve-bin-tool/actions/runs/13652954835/job/38165491473