Repository navigation
The folder doesn't display in the destination when pasting one premium blob folder which the name is 'New Folder' #3813
Description
Storage Explorer Version: 1.16.0
Build Number: 20201125.2
Branch: main
Platform/OS: Windows 10/ Linux Ubuntu 16.04/ MacOS Catalina
Architecture: ia32/x64
Regression From: Previous release(1.13.0)
Steps to Reproduce
- Expand one premium storage account (Premium StorageV2 or StorageV1)-> Blob Containers.
- Create a blob container -> Create a folder with the name 'New Folder' -> Upload one page blob to it.
- Copy the folder then paste it to any blob container.
- Check whether the folder displays in the destination.
Expected Experience
The folder displays well in the destination.
Actual Experience
The folder doesn't display in the destination.
Additional Context
- This issue doesn't reproduce when pasting one premium blob folder which the name is not 'New Folder' string.
- This issue doesn't reproduce for one regular blob folder and ADLS Gen2 blob folder.
- This issue also reproduces when cloning one premium blob folder which the name is 'New Folder'.
Activity
v-limu commentedon Dec 16, 2020
Add Info:
This issue reproduces for the folder name format 'X Y'. ( X and Y can be any character) For example as follows：
MRayermannMSFT commentedon Oct 6, 2021
v-limu
v-xianya commentedon Oct 8, 2021
Matthew Rayermann (@MRayermannMSFT)
Here is the direct link for the account:
storageexplorer://v=1&accountid=%2Fsubscriptions%2F92be7e56-8a60-427c-a3e3-0ebd54a827a1%2FresourceGroups%2FCTI-Kristine%2Fproviders%2FMicrosoft.Storage%2FstorageAccounts%2Fayantest&subscriptionid=92be7e56-8a60-427c-a3e3-0ebd54a827a1
MRayermannMSFT commentedon Oct 14, 2021
Appears to be a service side issue with using
+instead of%20in the delimiter query param. AzCopy is going to chase this one down. Moving to future until it is fixed.v-xianya commentedon May 17, 2024
Matthew Rayermann (@MRayermannMSFT)
On rel 1.34.0 build 20240517.1. The behavior of this issue has been changed. [FYI, the behaviors are the same as the Actual Experience on previous release 1.33.1]
It displays below errors after running the repro steps:
Error details:
{"name": null, "message": "\"failed to perform copy command due to error: cannot start job due to error: cannot list files due to reason GET https://apremium.blob.core.windows.net/atset01\\n--------------------------------------------------------------------------------\\nRESPONSE 400: 400 Value for one of the query parameters specified in the request URI is invalid.\\nERROR CODE: InvalidQueryParameterValue\\n--------------------------------------------------------------------------------\\n<?xml version=\\\"1.0\\\" encoding=\\\"utf-8\\\"?>\\n<Error><Code>InvalidQueryParameterValue</Code><Message>Value for one of the query parameters specified in the request URI is invalid.\\nRequestId:3a5c3e50-401c-0008-2f33-a80c4a000000\\nTime:2024-05-17T08:20:57.8339328Z</Message><QueryParameterName>include</QueryParameterName><QueryParameterValue>metadata,tags</QueryParameterValue><Reason>This query parameter value is invalid.</Reason></Error>\\n--------------------------------------------------------------------------------\\n.\\n\"" }