microsoft / microsoft/AzureStorageExplorer
AzCopy does not expose correct error information for deletes that failed b/c of leases
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.12.0
Build: 20200305.2
Branch: master
Platform/OS: Windows 10/ Linux Ubuntu 16.04
Architecture: ia32/x64
Regression From: Previous release (1.12.0)
Steps to reproduce:
- Expand one Non-ADLS Gen2 storage account -> Blob Containers.
- Create one blob container -> Upload one blob to it.
- Acquire lease for this blob -> Delete the leased blob.
- Check the activity log.
Expect Experience:
No 'Retry...' action displays.
Actual Experience:
Display an extra 'Retry...' action.
More Info:
- This issue also reproduces when deleting multi leased blobs.
- Show the below 'Retry Azcopy' dialog after clicking 'Retry...'.
- Related Bug: 2284
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 leased-blob deletion steps in the issue and inspect the activity log and Retry AzCopy dialog. Trace how the delete failure is reported and determine the expected behavior for single and multiple leased blobs. Done means lease-related delete failures no longer expose a Retry action.
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
- 35/100