Please open-source the `generate_completions.py` used for the v2 completions
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 42/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- python
- 领域
- documentation, tooling
调研方向
Start with evaluation/compute_pass_at_1.py, evaluation/execute_benchmark.py, the shipped completions/ directory, and the last generate_completions.py version in git history. Compare the documented scoring flow with the v2 model set and identify the missing generation details. Done means publishing the exact script or README specification covering prompts, sampling, response parsing, retries, and n=5 behavior.
由索引模型根据 Issue 内容生成。
描述
Please open-source the generate_completions.py used for the v2 completions
Thanks for releasing DevBench! The scoring side is fully reproducible —
running evaluation/compute_pass_at_1.py over the shipped completions/
reproduces the paper's numbers closely.
The generation side is not, because the script that produced the current
completions seems to be missing from the repo. So we can only re-score the
static files you shipped, not generate completions for a new model under the
same protocol or re-derive the paper's Pass@1 from scratch.
What's missing
generate_completions.pyis not in the tree at the pinned v2 revision
(831495a, "hardened v2: 1,800 tasks, 9 current-gen models").- The last version in git history targets an older model set (
gpt-4o,
gpt-4.1*,claude-3-7/4-sonnet,deepseek-v3/v3.1) — not the shipped v2
models (gpt-5.5/5.4-mini/5.4-nano,claude-opus-4-7,claude-sonnet-4-6,
deepseek-v4-pro,llama-4-maverick,mistral-medium-3.5,qwen3.6-27b). - The README says the FIM prompt is "defined in
evaluation/execute_benchmark.py",
but that file only contains the execution/scoring harness — no
prompt-construction or model-call code.
Why it blocks reproduction
With the documented max_tokens=800, current reasoning models spend the budget
on reasoning tokens and return empty content on many tasks (~40%+ empty in
my runs), whereas your shipped completions have a very low empty rate. So a
different generation setup must have been used, and we can't match it blindly.
Request
Could you open-source the exact generation script (or just specify it in the
README), including:
- The exact per-language system + user / FIM prompt template.
- Sampling params actually used, especially how reasoning models were
handled (default settings? whatmax_tokens?). - Response parsing / code-extraction logic.
- Empty-output/retry handling and the
n=5sampling details.
Even a lightly-cleaned version would make generation reproducible. Thanks!
- 主要语言
- Python
- 星标
- 13
- 派生
- 4
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoft/devbench 的其他 Issue
查看 microsoft/devbench 的全部 Issue
相似的 Issue
-
agent-ready documentation needs-triage
难度 1/5 1-3 小时 新手友好度 88/100
-
documentation
难度 1/5 1 小时以内 新手友好度 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" 未关闭
难度 1/5 1 小时以内 新手友好度 92/100
-
instance instance add
难度 1/5 1 小时以内 新手友好度 72/100
searxng/searx-instances#939 · 1 条评论 ·
-
area-deployment area-integrations triage:bot-seen
难度 2/5 半天 新手友好度 86/100