-
Notifications
You must be signed in to change notification settings - Fork 1.2k
🐛 fix: prevent list accumulation in multi-namespace cache implementation #3195
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Xuhui zhang <[email protected]>
Welcome @zxh326! |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: zxh326 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @zxh326. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
if err != nil { | ||
return err | ||
} | ||
allItems := []runtime.Object{} |
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.
While I agree this change makes sense, its a breaking one - Can we mark it as such?
/ok-to-test
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.
Do you have any suggestions?
This PR fixes an issue in the multi-namespace cache implementation where repeated calls to the
List()
method on the same list object would accumulate results instead of resetting the list each time. This happens because the current implementation extracts existing items from the provided list object, then appends new items to it, causing the list to grow with each call.The fix initializes a fresh empty slice for collected items instead of extracting from the existing list object.
fix #3194