Change UnixFS dag-pb protobuf field ordering
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
调研方向
首先阅读链接的 dag-pb 序列化格式规范以及对 IPIP-499 和 specs pull request 的引用,以了解兼容性和 profile 上下文。当排序提案、其对 wire format 的影响以及任何到 unixfs-v1-2026 的升级路径都得到明确规定并获接受时,工作即告完成。
由索引模型根据 Issue 内容生成。
描述
The .proto definition of a PBNode is this (spec):
message PBNode {
// refs to other objects
repeated PBLink Links = 2;
// opaque user data
optional bytes Data = 1;
}
Implementations are expected to write the repeated Links messages to the output buffer first, then the Data field, even though the field IDs are ordered the opposite way (not disallowed by the protobuf spec, though some off the shelf encoders will write in ID order).
When the PBNode represents a directory, the Links objects could be either flat directory entries, or HAMT shard entries - the information needed to ascertain this is contained in the Data field.
This means when processing an incoming PBNode message, we typically read all of the Links, and then use the Data to decide how to process them.
If we are performing a graph traversal, a streaming parser would let us process the PBNode message as it arrives, and to select the Link message we wish to traverse through or resolve to, however this is not currently possible since we need to process the Data field before we can return a Link. This can add significant overhead when there are many thousands of Links.
We should allow ordering the Data field first, this would enable the streaming use-case and help with IPFS code running in resource-constrained environments such as web browsers.
Since IPIP-499 we now have CID profiles which could be an upgrade path for the network. This proposal could be part of a unixfs-v1-2026 profile.
- 主要语言
- HTML
- 星标
- 1.2k
- 派生
- 250
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
ipfs/specs 的其他 Issue
-
need/triage
难度 2/5 1-3 小时 新手友好度 68/100
-
need/triage
难度 5/5 一周以上 新手友好度 30/100
-
dnslink:// URIs未关闭need/triage
难度 5/5 一周以上 新手友好度 30/100
-
难度 5/5 一周以上 新手友好度 35/100
-
need/triage
难度 3/5 1-2 天 新手友好度 55/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
volcano-sh/volcano#6323 ·
维护者通常 1 天内回复
-
area: facilitator bug complexity: trivial
难度 2/5 1-3 小时 新手友好度 70/100
accensa/x402-facilitator-stellar#709 ·
维护者通常 1 天内回复
-
resiliency: ParseRetryConditionMatch fails when HTTPStatusCodes or GRPCStatusCodes contain whitespace可能已有人在做 @patelshivani2283-lab 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
[Bug] maxConcurrent{Activity,Workflow,Nexus}TaskPolls are accepted but never applied可能已有人在做 @pcbeingused333 于 1 天前认领。 未关闭sdk-typescript
难度 2/5 1-3 小时 新手友好度 68/100
temporalio/sdk-typescript#2693 ·
维护者通常 1 天内回复