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
Fix race in vsphere cloud provider #90348
Conversation
When a go loop launches goroutines, it is a common mistake to assume that the routines can reference the loop value from their specific loop iteration. Actually, all goroutines share the same reference to the loop veriable, and they typically all see the last value. To correct this, the loop variable must be captured as a parameter to the anonymous func. This fix might eliminate the need for the retry logic below, but I do not have enough information to back that up. Signed-off-by: Jonathan Basseri <misterikkit@google.com>
/sig storage |
/lgtm |
/approve |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BaluDontu, divyenpatel, misterikkit 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 |
/retest Review the full test history for this PR. Silence the bot with an |
5 similar comments
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
What type of PR is this?
/kind bug
What this PR does / why we need it:
When a go loop launches goroutines, it is a common mistake to assume
that the routines can reference the loop value from their specific loop
iteration. Actually, all goroutines share the same reference to the loop
veriable, and they typically all see the last value.
To correct this, the loop variable must be captured as a parameter to
the anonymous func.
This fix might eliminate the need for the retry logic below, but I do
not have enough information to back that up.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: