microsoft / microsoft/AzureStorageExplorer

Keep the 'Retry Azcopy' dialog consistent when deleting several blobs with snapshots at one time between normal blobs and ADLS Gen2 blobs

Open
#4,696 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:beetle: azcopy error reporting :gear: adls gen2 :gear: azcopy :test_tube: testing
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Storage Explorer Version: 1.20.1
Build Number: 20210715.14
Branch: hotfix\1.20.1
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

  1. Expand an ADLS Gen2 storage account -> Blob Containers. (Make sure the setting ADLS Gen2 snapshots (Preview) is enabled)
  2. Create a blob container -> Upload two blobs.
  3. Create snapshot for the two blobs.
  4. Delete the two blobs -> There is a failed activity log.
  5. Click 'Retry...' -> Observe the 'Retry AzCopy' dialog.
  6. Repeat steps 1-5 for one non-ADLS Gen2 storage account.
  7. Check whether the two 'Retry AzCopy' dialog are consistent.

Expected Experience

The two dialog are consistent.

Actual Experience

The two dialog are inconsistent.
image
image

Additional Context

Similar bug: 2693

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failed activity retry flow for multiple snapshot-bearing blobs in both ADLS Gen2 and non-ADLS Gen2 accounts, then compare the two 'Retry AzCopy' dialogs shown in the issue. Trace the dialog entry point used after clicking 'Retry...' and make the two cases consistent; verify both flows on the listed platforms.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.