Clone and Rehydrate may overwrite blobs when destination checks fail
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 22/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- azure
- 領域
- cloud, desktop-dev
研究方向
Start in the Clone and Rehydrate flow, tracing how the destination-blob existence checks, the container check and the subsequent copy are sequenced, and how a failed blob check is interpreted as a missing destination. The payload names no specific files or tests, so locate them from those function names. Done means a reproduction with injected check failures, plus either a blocked Apply or an explicit overwrite confirmation, and the maintainers have agreed on the intended behaviour.
由索引模型根據 Issue 內容生成。
描述
Summary
Source inspection identified a potential data-loss risk in Clone and Rehydrate. If the destination-existence checks both fail, the operation may treat an existing blob as absent and overwrite it. This has not been reproduced, and no data loss has been verified.
Conditions to investigate
- The destination container exists and its initial container check succeeds.
- A blob with the selected destination name already exists.
- Both the destination-blob property check and the listing check fail, for example because of transient errors or permissions that allow the container check and copy but prevent blob reads and listing.
- A subsequent copy request succeeds.
Proposed reproduction (not yet run)
Use disposable test data, not a production account.
- Create an archived source blob and an existing destination blob.
- Arrange for both destination-blob existence checks to fail while allowing the initial container check and the subsequent copy to succeed. The exact permission configuration or failure injection still needs to be established.
- Open Clone and Rehydrate, enter the existing destination name, and observe whether Apply is enabled and whether the existing blob is overwritten.
Expected experience
If the destination cannot be checked, the operation should report the failure and avoid silently overwriting an existing blob.
Actual experience
Not observed. Source inspection suggests that failures of both blob-existence checks can be treated as a missing destination, enabling Apply, and that the subsequent copy has no overwrite condition or separate confirmation. In contrast, a failed container-existence check prevents Apply, although its message may say the container does not exist.
Environment and related report
Storage Explorer version, build, operating system, architecture, authentication method, and an exact reproducing permission setup have not been verified. A previous same-name warning report is closed; it did not describe failures of both existence checks.
- 主要語言
- 沒有語言資料
- 星號
- 458
- 分支
- 92
- 平均合併
- 17 小時 57 分鐘
- 30 天內合併 PR
- 4
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
microsoft/AzureStorageExplorer 的其他 Issue
-
難度 2/5 1-2 天 新手友好度 76/100
microsoft/AzureStorageExplorer#9186 ·
-
:globe_with_meridians: hard-coded string :globe_with_meridians: localization :test_tube: testing
難度 2/5 1-3 小時 新手友好度 68/100
microsoft/AzureStorageExplorer#9152 ·
-
難度 4/5 3-5 天 新手友好度 52/100
microsoft/AzureStorageExplorer#9235 ·
-
難度 4/5 3-5 天 新手友好度 45/100
microsoft/AzureStorageExplorer#9234 ·
-
難度 3/5 1-2 天 新手友好度 42/100
microsoft/AzureStorageExplorer#9232 ·
查看 microsoft/AzureStorageExplorer 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 87/100
GoogleCloudPlatform/cloud-foundation-fabric#4392 ·
維護者通常 1 天內回覆
-
Preserve database capacity during dev deployments可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 2/5 1-3 小時 新手友好度 72/100
world-federation-of-advertisers/cross-media-measurement#4870 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆
-
agent-self
難度 2/5 1-3 小時 新手友好度 78/100
yologdev/yoyo-evolve#1173 ·
-
難度 2/5 1-3 小時 新手友好度 83/100
PolicyEngine/policyengine-api#4270 ·
維護者通常 1 天內回覆