Usually if the first page is empty it means there are no results. This was assumed in several places in AzureFilesystem. The Azure docs do not guarantee this and we have evidence (GH-49043) that there can be subsequent non-empty pages. Applying `SkipStartingEmptyPages` on a paged response corrects this assumption.
| 1011 | // evidence (GH-49043) that there can be subsequent non-empty pages. |
| 1012 | // Applying `SkipStartingEmptyPages` on a paged response corrects this assumption. |
| 1013 | void SkipStartingEmptyPages(Blobs::ListBlobContainersPagedResponse& paged_response) { |
| 1014 | while (paged_response.HasPage() && paged_response.BlobContainers.empty()) { |
| 1015 | paged_response.MoveToNextPage(); |
| 1016 | } |
| 1017 | } |
| 1018 | void SkipStartingEmptyPages(Blobs::ListBlobsPagedResponse& paged_response) { |
| 1019 | while (paged_response.HasPage() && paged_response.Blobs.size() == 0) { |
| 1020 | paged_response.MoveToNextPage(); |
no test coverage detected