Blob paste and clone always fail on emulator connections
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- azure, typescript
Research direction
Start with PasteBlobs.ts:228 and compare its emulator handling with blob-extension/src/index.ts:650-657, using emulatorApiVersion at line 118 as context. Run the blob paste E2E cases mentioned in the issue. Done means blob paste and clone no longer fail on emulator connections and the UI does not offer an action that cannot succeed.
Written by the indexing model from the issue text.
Description
Problem
Blob paste and clone fail 100% of the time on emulator connections. The SAS builder requests the optional t (tag) permission, but emulator SAS is pinned to service version 2018-03-28, which predates that permission. The result is a client-side RangeError -- Azurite is never contacted.
Container-level paste is already gated for emulator connections, but blob-level paste is not, so the UI offers an action that cannot succeed.
Evidence
PasteBlobs.ts:228-- requests optionalt, branching on connection type rather than on whether the target is the emulatorblob-extension/src/index.ts:520-522-- pinsemulatorApiVersion(defined line 118) to2018-03-28blob-extension/src/index.ts:650-657-- the existing container-level gate,canPasteBlobContainerToBlobContainersNode, which has no blob-level equivalent
Suggested fix
Either omit the t permission when the target is the emulator, or extend the existing gate to blob-level paste so the action is not offered.
Found while automating the blob paste E2E cases.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
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.
More from microsoft/AzureStorageExplorer
-
:beetle: regression :copilot: copilot :test_tube: testing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/AzureStorageExplorer#9191 · 1 comment ·
-
Difficulty 2/5 1-2 days Newbie friendliness 76/100
microsoft/AzureStorageExplorer#9186 ·
-
:globe_with_meridians: hard-coded string :globe_with_meridians: localization :test_tube: testing
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/AzureStorageExplorer#9152 ·
-
:gear: attach :gear: sas :gear: sign-in
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/AzureStorageExplorer#9199 ·
-
Access Error Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
microsoft/AzureStorageExplorer#9198 ·
All issues in microsoft/AzureStorageExplorer
Similar issues
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
canonical/postgresql-watcher-operator#111 · 2 comments ·
-
bug needs triage receiver/azureblob
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
open-telemetry/opentelemetry-collector-contrib#51474 · 1 comment ·
-
Dependency Dashboard Open
Difficulty 1/5 Under an hour Newbie friendliness 60/100
IBM/paas-starter#5 ·