microsoft / microsoft/AzureStorageExplorer

The deleted items don't auto disappear if the delete action is not cancelled successfully

Open
#7,439 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:beetle: azcopy error reporting :gear: azcopy :gear: blobs :gear: files :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.32.0-dev (95)
Build Number: 20231019.3
Branch: rel/1.32.0
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Sonoma 14.0(Apple M1 Pro)
Architecture: x64/x64/x64
How Found: Ad-hoc testing
Regression From: Not a regression

Steps to Reproduce

  1. Expand one storage account -> Blob Containers.
  2. Open one blob container which contains items.
  3. Select one file -> Delete the file.
  4. Click the 'Cancel' action next to the delete activity log.
  5. There is a failed activity log.
  6. Check whether the deleted file auto disappears.

Expected Experience

  1. The deleted file auto disappears.
  2. Display '1 completed' in the activity log.

Actual Experience

  1. The deleted file doesn't auto disappear.
  2. Display '0 completed' in the activity log.

image

Additional Context

  1. The file disappears after manually refreshing.
  2. The error details as below, it shows 'Can't cancel, because it has already completed'.
    image

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

Start with the Blob Containers delete flow and the related activity log entry, reproducing the sequence with a blob selected and the Cancel action used. Trace how the failed activity is reported and how the container view is refreshed; done means the deleted file disappears without a manual refresh and the activity log reports 1 completed.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.