Found bug in ListBlobs when there are multiple segments being returned by Azure. #1
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
this fixes a bug where it goes into an endless loop if there are multiple sections because strNextMarker is never passed in the while loop and it just keeps grabbing the first section.
missed a coma
Ledridge
commented
Nov 9, 2023
Author
Ledridge
left a comment
Ledridge
left a comment
There was a problem hiding this comment.
This fixes a big bug I had been working around for a while.
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.
The call to the internal function was not passing the marker for Next Segment. This caused any call that had more than 1 segment to go into an endless loop re-grabbing the first segment every time.