Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

List pagination is broken

See original GitHub issue

Which service(blob, file, queue, table) does this issue concern?

blob

Which version of the Azurite was used?

mcr.microsoft.com/azure-storage/azurite:latest

Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)

DockerHub

What’s the Node.js version?

No idea

What problem was encountered?

When using ListBlobsFlatSegment to list blobs and there are more blobs than MaxResults, we must do further requests so long as the returned NextMarker is NotDone. I create 110 blobs, named 0…109. I do a list with MaxResults=100, and get back blobs 0…99 and a NextMarker of 99. I do another list using that marker, and get back no results, instead of the remaining 10 results.

Steps to reproduce the issue?

I have an open PR which demonstrates the problem: https://github.com/hashicorp/vault/pull/12057 TestAzureBackend_ListPaging works with Azure, when I set the environment variables AZURE_ACCOUNT_NAME and AZURE_ACCOUNT_KEY. It fails when running against Azurite, as described above, and as seen here: https://app.circleci.com/pipelines/github/hashicorp/vault/19003/workflows/775ca893-c275-474e-b32b-f6c4071671dc/jobs/240755 azurite-debug-logs.txt.gz

If possible, please provide the debug log using the -d parameter, replacing <pathtodebuglog> with an appropriate path for your OS, or review the instructions for docker containers:

-d "<pathtodebuglog>"

Please be sure to remove any PII or sensitive information before sharing!
The debug log will log raw request headers and bodies, so that we can replay these against Azurite using REST and create tests to validate resolution.