Skip to content

fix(services/azblob): reject unsupported start_after in list - #8510

Open
YuangGao wants to merge 1 commit into
apache:mainfrom
YuangGao:fix/list-reject-unsupported-start-after
Open

YuangGao wants to merge 1 commit into
apache:mainfrom
YuangGao:fix/list-reject-unsupported-start-after

Conversation

@YuangGao

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

Closes #8506.

Rationale for this change

azblob doesn't declare list_with_start_after, but its list silently dropped the option, so every lister started from the beginning. Reproduced against a real storage account: lister_with("").start_after("a") over a, b, c returned all three.

A check in CorrectnessCheckLayer would cover every service, but cos honors start_after only for versioned listing without declaring it, so a generic check would reject that working path. This PR fixes azblob and leaves the generic check as a follow-up.

What changes are included in this PR?

  • azblob list returns Unsupported when start_after is set.

Verified against a real storage account: the call now fails with Unsupported, and the azblob behavior suite passes (144/144).

Are there any user-facing changes?

Listing azblob with start_after now returns Unsupported instead of ignoring it.

Breaking changes

AI Usage Statement

AI-assisted implementation.

@YuangGao
YuangGao requested a review from Xuanwo as a code owner November 12, 2026 03:59
@github-actions github-actions Bot added releases-note/fix The PR fixes a bug or has a title that begins with "fix" services/azblob size:S This PR changes 10-29 lines, ignoring generated files. labels Nov 12, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

releases-note/fix The PR fixes a bug or has a title that begins with "fix" services/azblob size:S This PR changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

new feature: reject or implement unsupported start_after for Azure Blob listing

1 participant