The number of responses resulting in the Pull is not of the expected length when using BatchRequest

[epignatelli]

Description:

When using BatchRequests to make concurrent requests, the number of responses is both inconsistent and wrong.

How to replicate:

Use the test file in #12
Switch the toggle on and off a couple of times and check the number of elements that the Pull outputs. It will not be stationary.

Expected behaviour:

If 50 requests are used as input, 50 responses should be returned as output. Some of them can be null

[epignatelli]

Bumping to 2.5 RC as this is non critical.
The workaround is to not encapsulate a list of GetRequest into a BatchRequest before pulling.
This will make the requests serial, rather than parallel, but you'll get the expected results

[epignatelli]

Bumping again to 3.1 such that we have the space to solve this