feat(provenance): publish each provenance bundle to Kubo, best effort
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python
调研方向
Start by reading the implementation of record_run_provenance, the Kubo client, and StorageReference; the issue does not name their files or tests. Trace how a completed run stores its canonical bundle and how failures are recorded, then run the backend tests with a failing Kubo mock. Done means successful uploads are retrievable by CID, while Kubo failures preserve the run result and mark the bundle unpublished.
由索引模型根据 Issue 内容生成。
描述
Summary
After a provenance bundle is recorded, add it to the platform node and store the CID as a StorageReference.
Estimated size: M
Motivation
Gives bundles a content-addressed home that anyone can verify against the bundle hash.
Proposal
- After
record_run_provenance, add the canonical bundle JSON through the Kubo client and append aStorageReference. - Best effort: a Kubo failure is logged and flagged on the run; it never fails the job or discards the result.
- The CID covers the uploaded JSON bytes, not the canonical commitment, so verification must parse the bundle and compare
bundle_hash.
Acceptance criteria
- A completed run has a bundle retrievable by its CID.
- With Kubo down, the run still completes and the bundle is marked unpublished.
- A test proves the job result is preserved when publishing fails.
Dependencies
- #61
- #4 and the provenance PRs (#34 to #37) merged first.
Testing plan
- Backend tests with a failing Kubo mock.
Part of #43. Ground rules for the content layer: no secrets in the repo, content-layer failures must never block or discard quantum execution, and tests and docs ship with every PR.
- 主要语言
- Python
- 星标
- 2
- 派生
- 4
- 平均合并
- 6 小时 14 分钟
- 30 天内合并 PR
- 18
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
QMeshPy/distributed-quantum 的其他 Issue
-
enhancement good first issue helia storage tier-1
难度 2/5 1-3 小时 新手友好度 78/100
QMeshPy/distributed-quantum#53 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments research-spike tier-2
难度 4/5 3-5 天 新手友好度 55/100
QMeshPy/distributed-quantum#78 ·
维护者通常 1 天内回复
-
chain-integration enhancement payments research-spike tier-2
难度 3/5 1-2 天 新手友好度 66/100
QMeshPy/distributed-quantum#77 ·
维护者通常 1 天内回复
-
documentation good first issue kubo storage tier-1
难度 2/5 1-3 小时 新手友好度 42/100
QMeshPy/distributed-quantum#75 ·
维护者通常 1 天内回复
-
enhancement kubo storage tier-2
难度 4/5 3-5 天 新手友好度 56/100
QMeshPy/distributed-quantum#74 ·
维护者通常 1 天内回复
查看 QMeshPy/distributed-quantum 的全部 Issue
相似的 Issue
-
[Resource]: Lore未关闭resource-submission validation-passed
难度 1/5 1 小时以内 新手友好度 88/100
hesreallyhim/awesome-claude-code#3234 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
openminion/openminion#376 ·
维护者通常 1 天内回复
-
Type: ☹︎ Bug
难度 2/5 1-3 小时 新手友好度 78/100
posit-dev/great-tables#1028 ·
维护者通常 1 天内回复
-
integration: apple_tv
难度 2/5 1-3 小时 新手友好度 78/100
home-assistant/core#188282 · 1 条评论 ·
维护者通常 1 天内回复
-
A "since" range is worded as a career: "the past two seasons" says "regular season career (2025 on)"未关闭P4: low
难度 2/5 1-3 小时 新手友好度 65/100
jeffknupp/association#538 ·