-
Notifications
You must be signed in to change notification settings - Fork 485
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
fix(metadata): fix V2 API int overflow error on 32bit ARM build #2872
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2872 +/- ##
==========================================
+ Coverage 39.33% 40.12% +0.79%
==========================================
Files 166 172 +6
Lines 13961 14246 +285
==========================================
+ Hits 5491 5716 +225
- Misses 8140 8163 +23
- Partials 330 367 +37
Continue to review full report at Codecov.
|
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.
you need to also modify event.go
Since 32bits ARCH only support 2,147,483,647 as the maximum positive signed integer, so use math.MaxInt32 instead of the math.MaxUint32. Fix #2870 Signed-off-by: weichou <weichou1229@gmail.com>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
No problem, modified. |
recheck |
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.
LGTM
Fix #2870
PR Checklist
Please check if your PR fulfills the following requirements:
If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
What is the current behavior?
Golang build failed with 32bits ARCH
Issue Number: #2870
What is the new behavior?
Since 32bits ARCH only support 2,147,483,647 as the maximum positive signed integer, so use math.MaxInt32 instead of the math.MaxUint32.
Does this PR introduce a breaking change?
New Imports
Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information