-
Notifications
You must be signed in to change notification settings - Fork 3.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
ring: make ring.Buffer generic #93736
ring: make ring.Buffer generic #93736
Conversation
f475105
to
91a0fb4
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.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @ajwerner)
pkg/util/tracing/crdbspan.go
line 157 at r4 (raw file):
// verbose recording because of the span limit) are not part of this buffer; // they're in finishedChildren.Root.StructuredRecords. structured sizeLimitedBuffer[*tracingpb.StructuredRecord]
do these need to be pointers any more or were they only pointer because they had to be boxed in interface{}
anyway?
pkg/util/tracing/tracer.go
line 970 at r4 (raw file):
tagsAlloc [3]attribute.KeyValue childrenAlloc [4]childRef structuredEventsAlloc [3]*tracingpb.StructuredRecord
do
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.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @andreimatei)
pkg/util/tracing/crdbspan.go
line 157 at r4 (raw file):
Previously, andreimatei (Andrei Matei) wrote…
do these need to be pointers any more or were they only pointer because they had to be boxed in
interface{}
anyway?
I think they want to be pointers because the protoutil.Message
interface is implemented on the pointer and they're constructed as pointers, no? Also, for better or for worse, the ring.Buffer
doesn't have a mechanism to get a pointer into the buffer itself. If it did you'd have to be careful about lifecycles. I think it's better to leave them as pointers in this PR.
pkg/util/tracing/tracer.go
line 970 at r4 (raw file):
Previously, andreimatei (Andrei Matei) wrote…
do
?
91a0fb4
to
68f23cd
Compare
Epic: none Release note: None
68f23cd
to
3f3218d
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.
Reviewable status: complete! 1 of 0 LGTMs obtained
TFTR! bors r+ |
Build failed (retrying...): |
Build succeeded: |
Epic: none
Release note: None