microsoft / microsoft/AzureStorageExplorer

It would be better to display a helpful error on the failed activity log or the error details dialog when 'pasting/uploading' blobs to a secondary blob container

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

Nobody has claimed this yet.

:beetle: azcopy error reporting :gear: azcopy :gear: blobs :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.21.0-dev
Build Number: 20210817.3
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Big Sur 11.4
Architecture: ia32\x64
How Found: From running test cases
Regression From: Not a regression

Steps to Reproduce

  1. Expand one storage account which has GRS enabled -> Blob Containers.
  2. Right click one existing blob container -> Click 'Open Secondary Location'.
  3. Try to upload one blob to the secondary blob explorer.
  4. Check whether there is a helpful error in the activity log or the error details dialog.

Expected Experience

There is a helpful error in the activity log or the error details dialog.

Actual Experience

There is an error 'UnexpectedCancel' in the activity log and the error details dialog.
image

Error details:
{ "message": "\"UnexpectedCancel\"" }

Additional Context

We can get the error RESPONSE Status: 403 Write operations are not allowed from AzCopy log.
99f73c4e-e3bb-3648-52c6-0a8e55508697.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 upload to a secondary blob container using the listed steps, then compare the activity log and error details dialog with the AzCopy log showing the 403 write restriction. Trace where the UnexpectedCancel message is surfaced; done means the user sees a helpful error for this failed operation.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.