feat(vault): publish circuits to the vault
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 55/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- react, typescript
- 领域
- backend, full-stack
调研方向
Start by reading ShareToVaultButton and its existing use on the run, finance, risk, and options pages, then trace the circuit types and hooks plus circuit-library-client.tsx and circuit-detail-client.tsx. Find where users finalize a circuit and choose a share action location. Done means publishing all listed circuit fields, showing the existing pin flow, and verifying local library lookup by CID while preserving SSR isolation.
由索引模型根据 Issue 内容生成。
描述
Summary
Wire a share action for circuits so the Circuit Library has real content.
Estimated size: S
Current state in this repo
type: "circuit"is supported by the hooks, types,circuit-library-client.tsxandcircuit-detail-client.tsx.ShareToVaultButtonis only used on run, finance, risk and options pages.
Proposal
- Add the share action where a user finalizes a circuit (state the chosen location in the PR).
- Publish a circuit record: name, description, OpenQASM source, qubit count, gate count, author, publishedAt, tags.
- After publishing, show the same pin button flow used for runs.
Acceptance criteria
- A circuit shared by a user appears in their local Circuit Library and can be re-read by CID.
- The record contains the fields above.
- SSR isolation is preserved (no Helia import on the server).
Out of scope
- Network-wide discovery.
Dependencies
- None; can be picked up independently.
Testing plan
- Component test for the button; manual check of the SSR build.
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 小时 54 分钟
- 30 天内合并 PR
- 7
环境准备
- 提供 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 天内回复
-
chain-integration enhancement payments tier-2
难度 5/5 一周以上 新手友好度 35/100
QMeshPy/distributed-quantum#76 ·
维护者通常 1 天内回复
-
documentation good first issue kubo storage tier-1
难度 2/5 1-3 小时 新手友好度 42/100
QMeshPy/distributed-quantum#75 ·
维护者通常 1 天内回复
查看 QMeshPy/distributed-quantum 的全部 Issue
相似的 Issue
-
Validate non-divisible effective batch sizes in the Unsloth LoRA backend可能已有人在做 @debesh-biswas 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
-
`rx.Model` event arguments emit `PydanticDeprecatedSince20` once per payload key可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100
reflex-dev/reflex#7634 · 1 条评论 ·
维护者通常 2 天内回复
-
documentation
难度 1/5 1-3 小时 新手友好度 82/100
topoteretes/cognee#6239 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
ranaroussi/yfinance#3009 ·
维护者通常 1 天内回复
-
Test discovery aborts on GPU builds without cuStateVec: check_cuStateVec expects a failed result but set_config() now raises RuntimeError可能已有人在做 @dmeliksetian 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 84/100
Qiskit/qiskit-aer#2495 ·
维护者通常 1 天内回复