ListSharesSegment call's marker not working as expected

[nadundesilva]

Which version of the SDK was used?

latest (v0.8.0)

Which platform are you using? (ex: Windows, Linux, Debian)

Mac

What problem was encountered?

I have a storage account with file shares with soft delete enabled. I am trying to limit and list the fileshares iteratively in the storage account using the marker parameter. However, the marker value points to a deleted fileshare and this is causing the list call to not properly send the next set of results.

How can we reproduce the problem in the simplest way?

1. Create storage account with soft delete enabled
2. Create about 10 file shares and delete about 6 of them
3. Call the ListSharesSegment method passing in marker from previous call as well as MaxResults: 2
4. Note how the same set of results are returned.

The returned marker also points to a deleted share (I know this is opaque to us but doesn't seem like it's correct. But I could be wrong)

Have you found a mitigation/solution?

No. We have to list the full list of shares as of now

[zezha-msft]

@mohsha-msft could you please attempt a repro?

[mohsha-msft]

Hey @nadundesilva ,

Thanks for reaching out!
Let me try to reproduce the issue. But if you want to view the deleted shares, you can do that by specifying the include=metadata,snapshots,deleted parameter.

 ListSharesSegment(ctx, azfile.Marker{}, azfile.ListSharesOptions{Detail: azfile.ListSharesDetail{Deleted:true}})

[nadundesilva]

@mohsha-msft actually my requirement is to not include the deleted shares at all in the listing calls (When using the marker even though I do not specify the deleted option, the marker is pointing to a deleted share).

Also the SDK (version - v0.8.0) doesn't yet seem to have the deleted option.

[nadundesilva]

Any update on this ? @mohsha-msft

[nadundesilva]

Any chance we can look into this issue ? 🤔 @zezha-msft @mohsha-msft