-
Notifications
You must be signed in to change notification settings - Fork 900
Ensure that grequestx continuously make progress #6991
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
Signed-off-by: Joseph Schuchart <[email protected]>
Nice catch. |
Does this mean that grequests were, in general, broken? (i.e., never being advanced) |
yup. |
This is NEWS-worthy, then... |
@devreal Can you cherry-pick to the appropriate branches? |
I think only the extended grequests (see #24) were affected, the ones that come with a progress function. that are not in the MPI standard. AFAICS they are used internally by ROMIO but are not exposed to the user (unlike MPICH). The regular grequests should not be affected. I will cherry-pick to the release branches. |
Oh, if there's no way for the user to be exposed to this bug, then it's not worth cherry-picking. Specifically: are we using the extended grequests functionality in ROMIO? |
indeed, the normal grequest are having their query function called as expected. I wonder how is ROMIO working if we don't progress their requests as expected ? If this functionality used in the current code ? |
The handling of the grequest extensions is missing the release of the
in_progress
guard, causing requests not being polled after the first invocation.Signed-off-by: Joseph Schuchart [email protected]