microsoft / microsoft/AzureStorageExplorer
Unexpected cancel when cloning a blob in a secondary blob container
Open
Nobody has claimed this yet.
:beetle: azcopy error reporting
:gear: azcopy
:gear: blobs
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Things to do:
- Storage Explorer should disable the "Clone..." command in secondary containers.
- AzCopy can improve error reporting on this type of situation.
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 a clone operation in a secondary blob container, then trace the Storage Explorer "Clone..." command and the AzCopy error path. Done means the command is disabled for secondary containers and this situation produces improved AzCopy error reporting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100