-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Extend the monitor notification interface with endpoint id getter #15391
Extend the monitor notification interface with endpoint id getter #15391
Conversation
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.
I didn't know about the nil cast thing for compile time assertion on types. Nice :)
11235f2
to
c661536
Compare
test-me-please |
test-1.20-4.9 |
The sole test failure is |
test-1.20-4.9 |
1 similar comment
test-1.20-4.9 |
Memory allocation may occur for the big `Endpoint` struct if compiler optimizations are disabled. The official Go documentation recommends using `nil` type cast to ensure that (*T) implements an interface at compile time. Signed-off-by: Aditi Ghag <aditi@cilium.io>
Endpoint ID field is defined as 16-bit. However, the monitor notification interface converts this to 64-bit. To keep things consistent, and not break consumers of the interface, add a new method to the existing interface. Consumers then won't have to do unnecessary conversions while retrieving the original endpoint ID. Signed-off-by: Aditi Ghag <aditi@cilium.io>
c661536
to
626266a
Compare
One reason why I feel the test failures are unrelated because this PR only extends an existing interface. If there were issues related to run time cast due to which the interface isn't being satisfied, then we would've seen more obvious and deterministic failures. Since all the other tests had passed in earlier runs, I'm triggering only the |
test-1.20-4.9 |
Quay is down. Will need to re-try. |
test-1.20-4.9 |
Provisioning related issue. |
See commit message.