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

Storage Explorer not prompting for conflict resolution #1014

ghost opened this issue Dec 17, 2018 · 3 comments

Storage Explorer not prompting for conflict resolution #1014

ghost opened this issue Dec 17, 2018 · 3 comments


Copy link

@ghost ghost commented Dec 17, 2018

Storage Explorer Version: 1.6.0
Platform/OS: Windows 10
Architecture: i86
Regression From: It was working in prior releases.

Bug description
While coping blobs from one folder to the other, if the same blobs existed at the destination location, SE used to prompt for actions overwrite or skip. Now it just reports that the blob exists.

Steps to Reproduce

  1. Upload a few blobs to a container using some folder structure.
  2. Perform a copy/paste from with storage explorer to a different folder.
  3. Repeat step 2.

Expected Experience
In the activities window, a prompt would have come for action for the blobs, which exist at the destination location.

Actual Experience
The existing blobs were shown as error, and only retry or cancel option was presented.

Copy link

@craxal craxal commented Dec 17, 2018

Does the copy/paste take place in the same container? Does the account have hierarchical namespaces turned on or is using the standard blob service? Have you tried the Experimental/AzCopy feature turned on? That might work better.

Copy link

@ghost ghost commented Dec 18, 2018


The blobs have forward slashes in their names.

The reported behavior occurs both within same container and across containers.

I use AZ copy all the time for copying large volume of data, unattended.

I do have workarounds. I am simply repointing a broken functionality in v1.6.

@MRayermannMSFT MRayermannMSFT added this to the 1.6.2 milestone Jan 7, 2019
@MRayermannMSFT MRayermannMSFT added this to Committed in Storage Explorer via automation Jan 7, 2019
@MRayermannMSFT MRayermannMSFT self-assigned this Jan 7, 2019
@MRayermannMSFT MRayermannMSFT moved this from Committed to In Progress in Storage Explorer Jan 7, 2019
@MRayermannMSFT MRayermannMSFT moved this from In Progress to Done in Storage Explorer Jan 7, 2019
Copy link

@MRayermannMSFT MRayermannMSFT commented Jan 7, 2019

Fix merged into hotfix branch.

@craxal craxal removed this from Done in Storage Explorer Jan 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants