Sample finish_uploading_large_file uses the wrong sha1 and fails its resume check

未關閉
#249 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 3 天內回覆

@MatheoPaiva 已經在處理了。

開始於 2026年11月15日。

  • #262 來自 @MatheoPaiva —— 未關閉

評估

難度
2/5
預估耗時
1 小時以內
新手友好度
25/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
停滯
技術堆疊
java
領域
api

研究方向

Start with the setSha1 call at samples/src/main/java/com/backblaze/b2/sample/B2.java lines 576-579, then the resume check at core/src/main/java/com/backblaze/b2/client/B2LargeFileUploader.java line 127, which compares against getLargeFileSha1OrNull(). Open PR #262 already targets this, so review that before writing a patch. Done means the sample passes the value the check expects, so resume no longer fails with mismatch.

由索引模型根據 Issue 內容生成。

描述

What happens

The finish_uploading_large_file sample command sets the content source's sha1 from largeFileVersion.getContentSha1(). For a large file the server reports none there, while the resume check compares the source sha1 with the stored large_file_sha1 info value. The check then rejects the resume with a mismatch error.

Where

samples/src/main/java/com/backblaze/b2/sample/B2.java:576-579 (.setSha1(largeFileVersion.getContentSha1())); the check is at core/src/main/java/com/backblaze/b2/client/B2LargeFileUploader.java:127; the SDK itself notes that sha1 is none for large files at core/src/main/java/com/backblaze/b2/client/contentHandlers/B2ContentWriter.java:152.

Why it matters

Impact: Docs and messages (a sample command that does not work), loud. Severity: Low, because it only affects a sample command and fails with a clear error, and nothing is harmed.

How to check

Found by reading the code, not reproduced. Read the sample and the check: the check compares against getLargeFileSha1OrNull(), but the sample passes getContentSha1(). Using getLargeFileSha1OrNull() or computing the sha1 from the local file would match.

Version

Seen at v6.5.0. Present on the default branch: present.

主要語言
Java
星號
103
分支
23
平均合併
5 天 8 小時
30 天內合併 PR
3

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

Backblaze/b2-sdk-java 的其他 Issue

查看 Backblaze/b2-sdk-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。