microsoft / microsoft/AzureStorageExplorer
No clear error info displays when pasting a non-empty folder into another location where a blob/file with the same name exists
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Storage Explorer Version: 1.21.0-dev
Build Number: 20210812.1
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Big Sur 11.4
Architecture: ia32\x64
How Found: Exploratory testing
Regression From: Not a regression
Steps to Reproduce
- Expand one ADLS Gen2 storage account -> Blob Containers.
- Create a blob container -> Upload one blob A to the root.
- Create one folder B -> Create a sub-folder with the same name of the blob A under the folder.
- Upload one blob to the sub-folder.
- Copy the sub-folder and paste it to the root.
- Check whether we can get a clear error info from the activity log or AzCopy log.
Expected Experience
We can get a clear error info from the activity log or AzCopy log.
Actual Experience
We cannot get a clear error info from the activity log or AzCopy log.

Here is the AzCopy log:
a759dc88-9d42-4e41-7ca4-dd954d1b35c1.log
Additional Context
- A conflict dialog pops up when trying to paste the blob A into the folder B.

Display a failed activity log after applying replace.

Here is the AzCopy log:
f094e3ce-31e3-674e-5ef4-6de956319113.log
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the ADLS Gen2 folder-paste conflict described in the steps, then inspect the resulting activity log and AzCopy log. Done means both logs provide clear error information when a non-empty folder contains a blob name that conflicts at the destination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100