Content: replicate large files to your own devices over Carrier (ranged pull)

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

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
48/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
rust

研究方向

Read the replication and model Get code paths that use Carrier; the issue describes model downloads as pulling 64 KiB ranges from Carrier holders. Trace how those ranges are verified against a CID and how own-device replication currently hits Carrier import limits. Done means large content can be replicated to an own device by ranged pull over Carrier and verified against its CID, without the listed size caps.

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

描述

With each Home's Kubo running offline (0.8.0), replicas move only over Carrier. Pushing a copy to an own device is capped by Carrier's import limits (object import 64 MiB, exact import 200 MiB in one read, graph CAR 64 MiB). Above those caps, replication to an own device now fails with a clear refusal instead of travelling as a Kubo pin over bitswap. Model downloads already pull in 64 KiB ranges from Carrier holders and are unaffected.

Follow-up for 0.8.1: replicate large content by ranged pull from the holder over Carrier (as model Get does), verified against the CID, so own-device copies have no size cap.

主要語言
Rust
星號
6
分支
2
平均合併
1 天 3 小時
30 天內合併 PR
42

環境準備

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

從這裡開始

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

elastos/elastos-runtime 的其他 Issue

查看 elastos/elastos-runtime 的全部 Issue

相似的 Issue

更多 Rust Issue

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

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