-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
*: compatible with Go 1.14's checkptr #18189
Conversation
Codecov Report
@@ Coverage Diff @@
## master #18189 +/- ##
===========================================
Coverage 79.9187% 79.9187%
===========================================
Files 535 535
Lines 146535 146535
===========================================
Hits 117109 117109
Misses 20190 20190
Partials 9236 9236 |
e329d88
to
e3d27f6
Compare
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
PTAL @tiancaiamao |
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
/merge |
Your auto merge job has been accepted, waiting for:
|
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
What problem does this PR solve?
The Go 1.14 introduces new instrumentation to check that Go code is following unsafe.Pointer safety rules dynamically. The new flag -d=checkptr is enabled by default with the -race or -msan flags.
I have fixed memdb in #14972, and this PR will try to fix the remaining parts. And ngaut/unistore#402 is for unistore.
What is changed and how it works?
The newer version of
bbolt
has fixed this issue, so update it to the latest version. It doesn't change the version of etcd, andbbolt
is only used in tests, I think it is safe to do so.For
murmur3
hash package, change to https://github.com/twmb/murmur3Release note