-
Notifications
You must be signed in to change notification settings - Fork 406
pkg/virtual/workspaces/registry: fix panic sending to a closed channel #1889
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
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
/retest |
To stop the bleeding this seems reasonable however |
Currently, the projection watch interface closes its result channel in Stop(). This can cause a panic when the goroutine started in ResultChan() still tries to send data to the result channel which can be closed. This fixes it by making sure that the goroutine started in ResultChan() itself closes the channel once the delegate watch is done.
1fd7d35
to
bf418bd
Compare
/lgtm |
@davidfestal: you cannot LGTM your own PR. In response to this:
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. |
/lgtm |
/cherry-pick release-0.8 |
@ncdc: new pull request created: #1897 In response to this:
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. |
Summary
This PR should fix a panic in the
workspaces
virtual workspace.Related issue(s)
A panic is occuring in the
workspaces
virtual workspace, forcing the virtual workspace command to restart: