-
Notifications
You must be signed in to change notification settings - Fork 627
Fix deadlock issue. #2235
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 deadlock issue. #2235
Conversation
The deadlock was arising when components are initialized concurrently from different threads all waiting for `Lazy.get` to resolve which would never succeed.
Binary Size ReportAffected SDKs
Test Logs
NotesHead commit (92823b45) is created by Prow via merging commits: b485649 c9efaad. |
Coverage ReportAffected SDKs
Test Logs
NotesHTML coverage reports can be produced locally with Head commit (92823b45) is created by Prow via merging commits: b485649 c9efaad. |
@vkryachko: The following tests failed, say
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. I understand the commands that are listed here. |
* Fix deadlock issue. The deadlock was arising when components are initialized concurrently from different threads all waiting for `Lazy.get` to resolve which would never succeed. * Increase timeout, add licenses. * Added comments. Co-authored-by: Vladimir Kryachko <[email protected]>
The deadlock was arising when components are initialized concurrently
from different threads all waiting for
Lazy.get
to resolve which wouldnever succeed.