Wei Wei

> What's the status of that issue? I cannot use the newest `Azure.Storage.Blobs` (version `12.22.1`) which requires Blob API version `2024-11-04` introduced in version `3.32.0`. I don't want to downgrade...

@seankearney Blob Soft Delete is still not supported in Azurite, you can see it in Azurite readme file: https://github.com/Azure/Azurite#:~:text=Soft%20delete%20%26%20Undelete%20Blob Azurite welcome contribution! If would be great if you could help...

@seankearney Thanks for the reply! We actually already has issue like https://github.com/Azure/Azurite/issues/417 for blob soft delete.

@luyue14 The sas you generated is with "DataLakeSasBuilder", it's datalakegen2 SAS. And you can calling datalakeGen2 API with " DataLakeDirectoryClient". Azurite still not support datalakeGen2, so this does not work...

@anna-mazhar From the debug log, we see the error is "containerAcl.AccessPolicy cannot be null or undefined." Could you share the user scenario why you are trying to put a null/undefined...

@isra-fel Do you have any idea to improve the error handling to avoid cmdlet hang for above assembly conflict error? @david-garcia-garcia I believe you are not blocked for this issue...

@david-garcia-garcia We can understand your concern for the cmdlet not exit in this kind of error. The cmdlets can exist on common type of error, like error reported from storage...

@YunchuWang Thanks for the suggestion! However this might not be so appliable to Azurite. 1. We can start several Azurite instance on same host machine, with different (customized) ports. So...

@EmmaZhu Would you please help to look?

@kimjamia We set "question" label to it, since we don't know the root cause for this issue, so can't says this is a bug. @EmmaZhu Would you please help to...