-
Notifications
You must be signed in to change notification settings - Fork 648
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: add test for unint64 overflow on limit #5713
Conversation
// Nothing should be pruned, by passing in a limit of math.MaxUint64, overflow occurs | ||
// when initializing end to pruningSequenceStart + limit. This results in end always being | ||
// equal to start - 1 and thereby not entering the for loop. | ||
// We expect 10 acks, 10 receipts and pruningSequenceStart == 1 (loop not entered). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
crazy, so it doesn't panic, it just wraps around. I guess by construction this is safe. Should we add an in-line comment in the code in case someone tries to refactor it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
absolutely! Added a small note, feel free (you or anyone else) to expand on my dry-ness 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @DimitrisJim !!!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for checking this!
Awesome @DimitrisJim, nice one! |
Description
Wrap around is guaranteed in this case, ref https://go.dev/ref/spec#Integer_overflow. For signed ints this is also deterministic apparently.
closes: #XXXX
Commit Message / Changelog Entry
see the guidelines for commit messages. (view raw markdown for examples)
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
) or specification (x/<module>/spec/
).godoc
comments.Files changed
in the Github PR explorer.Codecov Report
in the comment section below once CI passes.