Incomplete listing on Backblaze S3 #113
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contrary to AWS, Backblaze adds `IsTruncated` (and others) only after the `CommonPrefixes` and `Contents`. It's pagination is 1000, what is a multiple of libs3's `MAX_COMMON_PREFIXES`. So if you have prefixes-only listing, you get 125 callbacks with 32 `commonPrefixes` in each. None of them will have valid `isTruncated` yet. And in `listBucketCompleteCallback`, where `isTruncated` is finally known, both `contentsCount` and `commonPrefixesCount` will be zero, and the callback will not be triggered.
Contributor
Author
|
Note that there's is probably a similar problem in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Contrary to AWS, Backblaze adds
IsTruncated(and others) only after theCommonPrefixesandContents. It's pagination is 1000, what is a multiple of libs3'sMAX_COMMON_PREFIXES. So if you have prefixes-only listing, you get 125 callbacks with 32commonPrefixesin each. None of them will have validisTruncatedyet. And inlistBucketCompleteCallback, whereisTruncatedis finally known, bothcontentsCountandcommonPrefixesCountwill be zero, and the callback will not be triggered.