-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
ranger: handle longlong overflow properly (#52365) #53496
ranger: handle longlong overflow properly (#52365) #53496
Conversation
Signed-off-by: ti-chi-bot <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-7.1 #53496 +/- ##
================================================
Coverage ? 73.5963%
================================================
Files ? 1211
Lines ? 381405
Branches ? 0
================================================
Hits ? 280700
Misses ? 82903
Partials ? 17802 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hawkingrei, winoros The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
/retest |
This is an automated cherry-pick of #52365
What problem does this PR solve?
Issue Number: close #45783
Problem Summary:
What changed and how does it work?
bigint would be returned if overflow error occurs, so
convertPoint
would adjust theexcl
of the boundary accordingly, and impossible ranges would be removed by consequentvalidIntervals()
.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.