det translator: classify and close the census's bare refused: LayoutError (9 programs, 1 estate; #5865 rank 2)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with the evidence policy in the issue and the census workflow in tests/tools/det_survey.py and tests/tools/gap_prevalence.py; inspect raise LayoutError sites in det/layout.py without reading census code. First classify the bare refusal from translator text and regenerate the aggregate page. If it is an engine gap, reproduce the construct synthetically or with a burned estate, then check whether the aggregate census count moves.
由索引模型根据 Issue 内容生成。
描述
Why
docs/language_status/gap_prevalence.md (#5865) ranks census refused: LayoutError 2nd in the close-next order. It refuses 9 programs whole in one census estate (era e2), and closing it would take the census from 17 to 26 of 40 whole (upper bound). Census today: 8 of 40 whole, flat since 2026-10-24.
This is the bare class: its message matched none of the named LayoutError families that #6613 itemised (_REFUSALS in tests/tools/gap_prevalence.py: VALUE not modelled / not a number, REDEFINES target, level without an 01, DATA DIVISION does not parse). We don't yet know which construct it is.
Do
- Classify, by tool only (evidence policy section 3: never open or read census code). Re-run the census survey (
tests/tools/det_survey.py/gap_prevalence.pycensus mode) and add a name-free_REFUSALSkey for the uncovered LayoutError message(s), built from the translator's own text indet/layout.py(raise LayoutErrorsites; L288raise LayoutError(why)is the generic one). Commit the regenerated page. - If the key is a source defect (e.g. text past column 72, #4735), give it an owner line saying so, as the missing-copybook row has. Not an engine gap; stop there.
- Otherwise fix the construct in
det/layout.pyfrom a synthetic or burned-estate reproduction, with register entries where IBM leaves it open. Check the census count moves (re-run, aggregates only).
Scope: frontier (ranked by #5865, not promoted). Part of #5865.
- 主要语言
- Python
- 星标
- 57
- 派生
- 11
- 平均合并
- 1 小时 46 分钟
- 30 天内合并 PR
- 972
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
squid-protocol/gitgalaxy 的其他 Issue
-
documentation
难度 2/5 1-3 小时 新手友好度 68/100
squid-protocol/gitgalaxy#8002 ·
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 78/100
squid-protocol/gitgalaxy#8000 ·
维护者通常 1 天内回复
-
documentation
难度 1/5 1 小时以内 新手友好度 82/100
squid-protocol/gitgalaxy#8001 ·
维护者通常 1 天内回复
-
documentation
难度 1/5 1-3 小时 新手友好度 84/100
squid-protocol/gitgalaxy#7998 ·
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 78/100
squid-protocol/gitgalaxy#7999 ·
维护者通常 1 天内回复
查看 squid-protocol/gitgalaxy 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 83/100
-
难度 2/5 1-3 小时 新手友好度 87/100
维护者通常 7 天内回复
-
good first issue
难度 2/5 1-3 小时 新手友好度 78/100
MTSWebServices/RecTools#330 ·
-
area: web priority: P1 story
难度 2/5 1-3 小时 新手友好度 76/100
nfiasco/Quant-Time-Machine#151 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
autowarefoundation/autoware_carla_scenario#2019 ·
维护者通常 1 天内回复