microsoft / microsoft/AzureStorageExplorer

There is a failed activity log with an error 'UnexpectedQuit' when cloning one blob with a name which contains more than 951 characters

Open
#4,752 2 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: 20210803.3
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Big Sur 11.4
Architecture: ia32\x64
How Found: Exploratory testing
Regression From: Not a regression

Steps to Reproduce

  1. Expand one storage account -> Blob Container.
  2. Select one blob container -> Upload one blob.
  3. Clone the blob with a long name which contains more than 951 characters.
  4. Check whether succeed to clone.

Expected Experience

Succeed to clone.

Actual Experience

There is a failed activity log with an error 'UnexpectedQuit'.
image

{ "message": "\"UnexpectedQuit\"" }

Additional Info

  1. This issue also reproduces when uploading one blob to directory which has a very long path.
    image
  2. Here are is the blob name which contains 952 characters.
    longname.txt

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 by reproducing the blob clone and upload scenarios described in the steps, then inspect the activity log reporting UnexpectedQuit. Done means cloning a blob with more than 951 characters and uploading to a very long directory path both succeed without a failed activity log.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.