-
Notifications
You must be signed in to change notification settings - Fork 4.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
Make an actual deep-copy of the state #7219
Conversation
Hi @jacksontj. Thanks for your PR. I'm waiting for a kubernetes 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/test-infra repository. |
/ok-to-test |
Unfortunately all the e2e tests are still blocked on kubernetes/kubernetes#79305 -- it made an error fatal which every test run hits (details in slack ) |
Before this patch this was creating a shallow copy, as the KVState was copied but the underlying map (Records) wasn't. Related to kubernetes#7134
Thanks for tracking down and fixing @jacksontj ... I think we finally got the e2es working again, following @zetaab 's suggestion of testing with 1.15 (and I have a fix for the underlying issue in 1.16 also). /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jacksontj, justinsb The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…9-upstream-release-1.13 Automated cherry pick of #7219: Make an actual deep-copy of the state
…9-upstream-release-1.14 Automated cherry pick of #7219: Make an actual deep-copy of the state
…9-upstream-release-1.12 Automated cherry pick of #7219: Make an actual deep-copy of the state
Before this patch this was creating a shallow copy, as the KVState was
copied but the underlying map (Records) wasn't.
Fixes #7134
Go playground showing the issue with the previous copy mechanism: https://play.golang.org/p/0-NAWVpbR7s