microsoft / microsoft/AzureStorageExplorer

Fail to delete one ADLS Gen2 folder/file whose name contains '#,%,?'

Open
#7,692 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:beetle: regression :gear: adls gen2 :gear: azcopy :grey_question: external :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.33.0-dev (96)
Build Number: 20240120.3
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.2(Apple M1 Pro)
Architecture: x64/x64/arm64
How Found: Exploratory testing
Regression From: Previous release (1.32.1)

Steps to Reproduce

  1. Expand one ADLS Gen2 storage account -> Blob Containers.
  2. Create a blob container -> Create a folder using the name '#%?'.
  3. Try to delete the folder.
  4. Check whether succeeds to delete it.

Expected Experience

Succeed to delete the folder.
image

Actual Experience

Fail to delete the folder.
image

Additional Context

Here is the AzCopy log:
093ab72e-a2e2-0948-6b5d-a4c50f08f266.log

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 deletion failure in an ADLS Gen2 blob container using the folder name '#%?' on the listed platforms, then inspect the linked AzCopy log for the failing operation. Done means the folder or file deletes successfully when its name contains '#', '%' or '?', matching the expected experience.

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
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.