[Task][RFC]: Qualify the integrated benchmark study upload and dashboard contract
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 38/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python, typescript
调研方向
Start with the linked RFC, then inspect study_projection.py, benchmark_study.py, and benchmark-study-page.tsx to map its acceptance criteria to the existing contract, CLI, and dashboard. Exercise the installed or source CLI and actual dashboard as the issue requires. Done means reporting the integrated revision and passed, failed, and untested evidence, reconciling the delivery checkpoint, and identifying any remaining gates; close the accepted scope only if the v0 criteria are satisfied.
由索引模型根据 Issue 内容生成。
描述
Outcome / 目标
验收 benchmark study 上传、回读与看板完整链路。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree.
Canonical design: RFC. Roadmap: S11/S12, under #4574. Design acceptance is distinct from implementation, live qualification and promotion.
Current boundary
Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim.
The contract/reducers, local upload CLI and read-only dashboard already exist; #3878 binds case insights to terminal runs. Treat this as integrated acceptance and current-checkpoint reconciliation, not a new dashboard or uploader.
Work remaining
- Map RFC acceptance to the shipped CLI → local upload/readback → derived campaign/arm/case/run views and close any evidenced integration gaps.
- Reconcile the RFC delivery checkpoint with that evidence. If every v0 criterion is already satisfied, close with evidence rather than inventing features.
Ownership and ongoing work
Reuse #3243 and existing benchmark-toolkit owners. PR #4439 is a separate evaluation program, not work to duplicate here. External sink transport requires its own existing authorization and lifecycle.
Contribution route: available for a bounded proposal/PR within this RFC. Name the intended milestone and exact files in a claim comment so simultaneous contributors do not duplicate work.
Acceptance
- Simple and factorized synthetic studies round-trip without losing countability, metric, effort, fidelity or provenance; denominators and provisional status remain visible.
- Replay/supersession, duplicate manifests, invalid identity, unknown record kind and forbidden evidence fail or reconcile according to the existing contract.
- Exercise the installed/source CLI and actual dashboard; no new scoring, real benchmark jobs, remote upload or leaderboard submission.
- Reconcile the RFC's current delivery checkpoint and this issue with the integrated revision, commands, passed/failed/untested evidence and remaining gates. Close the accepted scope only; no claim that a merged PR alone completes the RFC.
Starting points and delivery boundary
- loopx/capabilities/benchmark_toolkit/study_projection.py
- loopx/cli_commands/benchmark_study.py
- apps/presentation/dashboard/src/views/benchmark-study-page.tsx
Base: latest main. Reuse the existing typed owner and provider boundaries. Include affected CLI/frontend/Lark companions; verify real entrypoints and backend where changed. Preserve existing first-screen review and maintainer merge gates. Public artifacts contain only synthetic/public-safe evidence, no private operational state. This task does not authorize provider promotion, benchmark launches, release/deployment or unrelated protected effects.
- 主要语言
- Python
- 星标
- 6.2k
- 派生
- 596
- 平均合并
- 6 小时 44 分钟
- 30 天内合并 PR
- 915
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
loopx-project/loopx 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
loopx-project/loopx#6842 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
loopx-project/loopx#6108 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
loopx-project/loopx#5688 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 60/100
loopx-project/loopx#5632 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
loopx-project/loopx#5443 · 1 条评论 ·
维护者通常 1 天内回复
查看 loopx-project/loopx 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
ansys/pyansys-common-mcp#213 ·
维护者通常 3 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 67/100
freedomofpress/dangerzone#1594 ·
维护者通常 3 天内回复
-
priority:P1 status:in-review type:bug
难度 2/5 1-3 小时 新手友好度 75/100
randomparity/kdive#3317 · 1 条评论 ·
维护者通常 1 天内回复
-
area:ci
难度 1/5 1 小时以内 新手友好度 90/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
mesonbuild/meson#16281 ·
维护者通常 1 天内回复