Failed large file upload leaves the file unfinished and the error has no file id
維護者通常 3 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
Start in core/src/main/java/com/backblaze/b2/client/B2LargeFileUploader.java: read uploadLargeFile (around lines 73-80) and the catch and finally blocks in uploadPartsAndFinish (around lines 241-252), which cancel part futures but never the large file. Before changing anything, decide whether leaving the file for resume is intended, since the issue asks for that decision. Done means the failure path either cancels the large file or includes its file id in the thrown error and javadoc, with a test that fails one part and checks unfinishedLargeFiles.
由索引模型根據 Issue 內容生成。
描述
What happens
After uploadLargeFile() has started the large file, any failure (a failed part, an interrupt, a rejected task) is rethrown without calling cancelLargeFile. The unfinished large file stays on the server, and the exception does not mention its file id, so the caller cannot easily clean it up or resume it.
Where
core/src/main/java/com/backblaze/b2/client/B2LargeFileUploader.java:73-80 (start the large file) and :241-252 (the catch and finally blocks, which cancel the part futures but never the large file). Public methods B2StorageClient.unfinishedLargeFiles and cancelLargeFile exist.
Why it matters
Impact: Left behind (an unfinished large file stays on the account), loud. Severity: Medium, because it is only reached after a failure partway through an upload, and the caller can find and cancel the file through unfinishedLargeFiles and cancelLargeFile.
How to check
Found by reading the code, not reproduced. Read uploadLargeFile and uploadPartsAndFinish: there is no call to cancel the large file on any failure path. Failing one part in a test and then listing unfinished large files should show the leftover file. If leaving the file is intended so that finishUploadingLargeFile can resume it, the javadoc could say so and include the file id in the error.
Version
Seen at v6.5.0. Present on the default branch: present.
- 主要語言
- Java
- 星號
- 103
- 分支
- 23
- 平均合併
- 5 天 8 小時
- 30 天內合併 PR
- 3
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
Backblaze/b2-sdk-java 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 78/100
Backblaze/b2-sdk-java#248 ·
維護者通常 3 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
Backblaze/b2-sdk-java#247 ·
維護者通常 3 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
Backblaze/b2-sdk-java#246 ·
維護者通常 3 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
Backblaze/b2-sdk-java#245 ·
維護者通常 3 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
Backblaze/b2-sdk-java#242 ·
維護者通常 3 天內回覆
查看 Backblaze/b2-sdk-java 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
IETF-Hackathon/pqc-certificates#351 ·
維護者通常 2 天內回覆
-
bug(core): skip_nodes.json is missing SELECT and PRE, causing Python and Java to insert separators into dropdown options and preformatted text可能已有人在做 @Bhumit267 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 85/100
維護者通常 1 天內回覆
-
ExceptionThrowShouldUseContext: NullPointerException on a catch block inside an annotation type可能已有人在做 @Carbon14-48 今天認領。 未關閉approved
難度 2/5 1-3 小時 新手友好度 72/100
checkstyle/checkstyle#22784 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
維護者通常 1 天內回覆