-
Notifications
You must be signed in to change notification settings - Fork 7
Wait methods fixes [part 1] #139
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
75e5c49
to
f18a1ba
Compare
f18a1ba
to
d07b5e3
Compare
Regarding #141 - it's good idea to do so. But for now, let's simply fix |
Let's pull out the code for checking the readiness of requested and count responses in `waitAll` and `waitCount` correspondingly. We will further use these helpers to check the futures before waiting. Needed for tarantool#133
10ba188
to
762d103
Compare
762d103
to
e76a1e0
Compare
Currently, `waitAll` and `waitCount` unconditionally `wait` instead of checking response readiness. If there are no more responses, it will cause them to hang indefinitely. To fix this, let's check the response readiness first. We should also move the time start to the beginning of the waiting loop, since the initial response checking overhead should not be accounted for the waiting time. Closes tarantool#133
Currently, we do not check the return code of `wait` in `waitAny`. If there is an error, we must log it and return a `nullopt`. Closes tarantool#121
e76a1e0
to
804c0f5
Compare
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.
Thank you for the patch! Glad to see the connector is thriving!
LGTM.
This patchset fixes some bugs with the Connector
wait*
methods.Closes #121
closes #133