Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to perform Delete action for one ADLS Gen2 blob which name contains non-English characters #980

Closed
v-xuanzh opened this issue Dec 10, 2018 · 7 comments
Assignees
Milestone

Comments

@v-xuanzh
Copy link

@v-xuanzh v-xuanzh commented Dec 10, 2018

Storage Explorer Version: 1.7.0
Platform/OS Version: Windows 10/ MacOS High Sierra/ Linux Ubuntu 16.04
Architecture: ia32
Build Number: 20190312.3
Regression From: Not a regression

Steps to Reproduce:

  1. Expand one ADLS Gen2 account -> Blob Containers node.
  2. Open one blob container ->Upload one blob which name contains non-English like '五星红旗'.
  3. Right click the uploaded blob then try to delete it.

Expected Experience:

The uploaded blob can be deleted successfully.

Actual Experience:

Unable to delete the uploaded blob with the error.
image

More info:

This issue doesn't reproduce for non - ADLS Gen2 blobs.

@larrylieberman

This comment has been minimized.

Copy link
Member

@larrylieberman larrylieberman commented Feb 25, 2019

I am seeing this exact error today, on attempting to open "Manage Access" on an object, with this version:

Version: 1.6.2
Platform: macOS
Architecture: x64
Build Number: 20190108.2
Commit: b3158558
Support Id: b01b4d84-35e5-b355-9f36-fc1fb42908dd

The file object has a name with square brackets in it " [ ] ". This is problematic, because Azure Data Factory, when orchestrating files out of a relational DB, defaults to using a filename with these characters.

If I change the filename to remove the [] characters, "Manage Access" works as expected.

@v-xuanzh v-xuanzh changed the title Unable to perform Manage Access/Delete/Get properties actions for one ADLS Gen2 blob which name contains non-English characters Unable to perform Delete action for one ADLS Gen2 blob which name contains non-English characters Mar 13, 2019
@MRayermannMSFT MRayermannMSFT added this to the 1.8.0 milestone Mar 13, 2019
@MRayermannMSFT MRayermannMSFT added this to Committed in Storage Explorer via automation Mar 13, 2019
@MRayermannMSFT MRayermannMSFT self-assigned this Mar 15, 2019
@MRayermannMSFT MRayermannMSFT moved this from Committed to In Progress in Storage Explorer Mar 15, 2019
@MRayermannMSFT

This comment has been minimized.

Copy link
Member

@MRayermannMSFT MRayermannMSFT commented Mar 15, 2019

Hi @larrylieberman , just wanted to update you on this issue. There appears to be a bug in the Storage SDK we are using. We're looking to either find a workaround or get the SDK update in time for 1.8.0. Thank you for your patience!

@MRayermannMSFT MRayermannMSFT moved this from In Progress to Blocked in Storage Explorer Mar 15, 2019
@arrayelement

This comment has been minimized.

Copy link

@arrayelement arrayelement commented Mar 18, 2019

I am seeing this issue, but with a file that contain all English characters.
The json returned from Storage Explorer 1.7.0 is attached
ase_delete_blob_error_json.txt

@jinglouMSFT

This comment has been minimized.

Copy link

@jinglouMSFT jinglouMSFT commented Mar 18, 2019

@arrayelement Are you running behind a proxy and using ADLS Gen2? If so, you might have run into a bug in delete that uses axios, which is a different bug. Please let us know if this is the case. Thanks.

@arrayelement

This comment has been minimized.

Copy link

@arrayelement arrayelement commented Mar 19, 2019

@jinglouMSFT Yes I am running behind a proxy and using ADLS Gen2 via Storage Explorer 1.7.0 I saw in the SE 1.7.0 release notes that some proxy issues were being addressed but that they are sill being refined. Hope the next release of storage explorer has these issues fixed. Looks like @MRayermannMSFT previous post might be addressing this issue in SE 1.8.0.

@jinglouMSFT

This comment has been minimized.

Copy link

@jinglouMSFT jinglouMSFT commented Mar 19, 2019

@arrayelement yes, the fix will be in 1.8.0 for sure. Let us know if you are interested in a private build to unblock you from deleting. Thanks.

@MRayermannMSFT

This comment has been minimized.

Copy link
Member

@MRayermannMSFT MRayermannMSFT commented Mar 26, 2019

A fix for the issue where some things don't work for ADLS Gen2 blobs that have unicode chars in the name has been checked into master and will be available in 1.8.0. This fix does not address any of remaining proxy issues with ADLS Gen2. A fix for those is still a ways away/depdendent on other teams unfortunately. Anyway, closing this issue since it is fixed.

Storage Explorer automation moved this from Blocked to Done Mar 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
5 participants
You can’t perform that action at this time.