Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The error doesn't disappear after typing a blob name which already exists into 'Destination blob name' on the 'Clone and Rehydrate' dialog #6655

Closed
v-xianya opened this issue Mar 10, 2023 · 3 comments
Assignees
Labels
🪲 regression Issue was working in a previous version 🧪 testing Found through regular testing ✅ merged A fix for this issue has been merged
Milestone

Comments

@v-xianya
Copy link
Member

Storage Explorer Version: 1.29.0-dev
Build Number: 20230310.1
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Ventura 13.2.1 (Apple M1 Pro)
Architecture: ia32/x64
How Found: From running test cases
Regression From: Previous release (1.28.1)

Steps to Reproduce

  1. Expand one storage account -> Blob Containers.
  2. Create a blob container -> Upload two blobs.
  3. Change one blob's access tier to 'Archive'.
  4. Right click the archived blob -> Click 'Clone and Rehydrate...'.
  5. Type the other blob's name into the 'Destination blob container' field -> Lose focus on the field.
  6. Check whether the error disappears.

Expected Experience

The error disappears.
image

Actual Experience

The error does not disappear.
image

Additional Context

  1. This issue also reproduces for 'Copy and Rehydrate' dialog.
  2. The error should disappear according to the description 'If a blob with the specified name already exists, the existing blob will be overwritten.' in the dialog.
@v-xianya v-xianya added 🧪 testing Found through regular testing 🪲 regression Issue was working in a previous version labels Mar 10, 2023
@JasonYeMSFT JasonYeMSFT self-assigned this Mar 10, 2023
@JasonYeMSFT JasonYeMSFT added this to the 1.29.0 milestone Mar 10, 2023
@JasonYeMSFT
Copy link
Contributor

JasonYeMSFT commented Mar 10, 2023

Showing the validation error is the expected behavior. We want to prevent people from overwriting data even if we have warned them about it. I will remove the description about the overwrite.

@JasonYeMSFT
Copy link
Contributor

This is related to the fix of #6623. Beware that since the validation is async, it's still possible to rush applying the change before we are able to detect the conflict. We think that's an edge case so we won't do anything to prevent that.

@v-xianya
Copy link
Member Author

Verified this issue on the build main 20230312.3. The description has been removed. So, we are going to close it.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🪲 regression Issue was working in a previous version 🧪 testing Found through regular testing ✅ merged A fix for this issue has been merged
Projects
None yet
Development

No branches or pull requests

2 participants