-
Notifications
You must be signed in to change notification settings - Fork 111
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
RSDK-420 add default timeout on client resources call #1574
Conversation
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.
LGTM. Good catch. Why isn't it the case though that the resources call fails due to a broken pipe?
Or is this refactor because status calls resources? |
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.
lgtm
not exactly sure either. might look a bit more before merging in |
|
if we lose connection in the middle of a status refresh, we never return because of the lack of a timeout.
this causes the reconnection logic to hang (the status refresh holds a lock and we never give it up)
cc @Fahmina