Change Details

This will read the next link from the api response. It so happens that sometimes, the next link stays the same between consecutive api calls... Thus stopping the listing even though there "could" still exist data to list. This tries to continue by trying one last step, shifting the next index detected to 1 day in the future (creating a small hole). As a note, in regards to bitbucket, experiments below period shift of "one day in the future" bear no success. Related T1826 Depends D1633

We compute the next target index from the api. But did not re-urlencode it. The bitbucket lister answered to this inconsistently... Thus creating next link identical to the current one... Thus making the lister refuse to continue further). This fixes that behavior re-urlencoding correctly the index. Related T1826 Depends D1633

This will readWe compute the next link from the api response. It so happens thattarget index from the api. sometimes, the next link stays the same between consecutive api calls... ThusBut did not re-urlencode it. stopping the listing even though there "could" still exist data to list. This tries to continue by trying one last step, shifting the next index detectedThe bitbucket lister answered to this inconsistently... to 1 day inThus creating next link identical to the future (creating a small holecurrent one... Thus making the lister refuse to continue further). As a note, in regards to bitbucket, experiments below period shift of "one day in the future" bear no successThis fixes that behavior re-urlencoding correctly the index. Related T1826 Depends D1633