[12.x] Ensure HTTP batch results are returned in the same order as requested #57483
+8
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using the
Http::batchmethod (#56946), the results are currently sorted in the order that the responses came back, rather than the order that the requests were defined:While the keys are maintained, the results array is no longer a list, and the iterating order is likely unexpected.
This differs from the
Http::poolmethod, which always returns the results in the same order:This PR fixes this by sorting the results before they are returned, respecting any requests named with the
asmethod.I wasn't able to write a good test for this without hitting an external URL, because faked requests don't run async and always return in the correct order. I added a comment in lieu of a test.
I can confirm the following test passes (but would slow down the test suite and could be flaky):