search

microsoft / AzureStorageExplorer

Easily manage the contents of your storage account with Azure Storage Explorer. Upload, download, and manage blobs, files, queues, tables, and Cosmos DB entities. Gain easy access to manage your virtual machine disks. Work with either Azure Resource Manager or classic storage accounts, plus manage and configure cross-origin resource sharing (CORS) rules.
Creative Commons Attribution 4.0 International
364 stars 85 forks source link

'0 items transferred' shows in the activity log if not all transfers are selected on the 'Retry Azcopy' dialog regardless of whatever option is selected in the Overwrite part #8002

Open v-kellyluo opened 2 weeks ago

v-kellyluo commented 2 weeks ago

Storage Explorer Version: 1.35.0-dev (98) Build Number: 202406012.1 Branch: main Platform/OS: Windows11/Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.5(Apple M1 Pro) Architecture: arm64/x64/x64/arm64 How Found: Ad-hoc testing Regression From: Not a regression

Steps to Reproduce

  1. Expand one storage account (make sure the blob versioning is enabled) -> Blob Containers.
  2. Create one blob container -> Upload one blob -> Modify the blob 2 times.
  3. Switch to versions view -> Download all versions.
  4. Download them to same destination again -> Select 'Do not download -> Apply to All Conflicts'.
  5. Click 'Retry...' next to the failed activity log -> Uncheck one transfer -> Select 'Enable overwrite' option -> Click 'Retry Selected'.
  6. Check whether '1 items transferred' shows in the activity log.

Expected Experience

'1 items transferred' shows in the activity log.

Actual Experience

'0 items transferred' shows in the activity log. image

Additional Context

  1. Related issue: 5570.
  2. If select 'Prompt for overwrite' option, no conflict dialog pops up.
  3. If select 'Enable overwrite' option, '0 items transferred' shows in the activity log.
  4. If select 'Disable overwrite' option, there is a successful activity log.
craxal commented 2 weeks ago

@RichardMSFT Since this isn't a regression, you don't need to prioritize a fix for this for 1.35.0.