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
-
難度 1/5 1 小時以內 新手友好度 72/100
slavakurilyak/awesome-ai-agents#845 ·
維護者通常 1 天內回覆
-
tests: pin that the atomic writers in utils/paths.py stage the temporary file in the target's directory可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉difficulty:2 enhancement good first issue
難度 1/5 1-3 小時 新手友好度 92/100
MakazhanAlpamys/Soup#2178 ·
維護者通常 1 天內回覆
-
[BUG] dcg.waggr permutation p-values are folded twice, so near-zero scores get the smallest p-values未關閉
難度 2/5 1-3 小時 新手友好度 75/100
scverse/rapids-singlecell#854 ·
維護者通常 1 天內回覆
-
Slang input: int8_t4_packed and uint8_t4_packed are copied into CrossGL可能已有人在做 @ninglinLiu 今天認領。 未關閉area:frontend backend:slang bug direction:input
難度 2/5 1-3 小時 新手友好度 70/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 85/100
維護者通常 13 天內回覆