Stripes-connect fetches past end when record-count is one less than multiple of perRequest
Description
As described in , an off-by-one error in stripes-connect means that when it's dealing with a result-set whose total size is one less than an exact multiple of perRequest, it tries to fetch an additional, unnecessary page.
What is the point of pushing this into sprint16 when it's already closed?
Jason Skomorowski June 9, 2017 at 3:06 PM
It was even dumber than that, sorry. But now the code and the test properly cover the not-unlikely case where more records are requested than available.
As described in , an off-by-one error in stripes-connect means that when it's dealing with a result-set whose total size is one less than an exact multiple of
perRequest, it tries to fetch an additional, unnecessary page.