Census mock trial: take the 40 census programs from 8 whole to 40 of 40 accounted, measured by the tool only
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 25/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- python
- 領域
- devtools, testing-qa
調査の方向性
Read the census protocol and ledger in this issue, then follow #5649 and the T0 instructions for cics_census.py survey and gap_prevalence.py. The work spans multiple translator gap classes and depends on fixes merging before each measurement. Done means all 40 programs are either translated whole or recorded as named source or clone problems, with aggregate ledger results published within the 14-day time box.
索引モデルが issue の本文から書いたものです。
説明
Owner request 2026-11-04: treat the 40 census programs (9 public repos excluded from the blind study, never burned, counted by tools only under opaque labels) as a mock trial of the engine. Write-up: https://claude.ai/artifact/9CJkXtuprzxzRne4bty3dy
Baseline (last real survey 2026-10-24, 6758295f2 / #6361)
8 of 40 translate whole (20%). Of the 32 blocked: 13 only by source / clone problems (missing estate copybooks 9, undeclared items #7647, ISPF screens #7645), 17 only by translator gaps, 2 by both. On the 25 programs with no source or clone problem: 8 of 25 (32%).
Predictions (frozen before the first fix)
- Translator work alone takes the census to 25 whole (62%); the other 15 end as named source / clone problems: 40 of 40 accounted.
- The tool's coverage-if-closed (upper bounds; they count the missing-copybook gap as closable): top 1 -> 17, top 3 -> 20, top 5 -> 29, top 10 -> 32.
- Cost: 9 translator gap classes x ~4-5 PRs per class (calibrated on #6876: 17 programs, 8 classes, 35 PRs, 6 days) = 35-45 PRs, 6-9 days at two workers.
Protocol
- First (owner 2026-11-04): #5649 -- the translator consumes the engine's record layouts (routed to nyx). The T0 re-survey waits until #5649 has merged; T0 then measures main with #5649 in, and the ledger notes it.
- T0: re-survey the census at current main with no census-targeted change (
cics_census.py surveyover the census repos, thengap_prevalence.py --census-survey ... --census-corpora ... --write); post the rate here. The 10-24 -> T0 delta is what the burned-estate work did for unseen code. - Nobody reads census source. A fix gets the gap label, the IBM manual page and the owning issue, and proves itself on our own test (a cics-crucible program or a fixture), never a census excerpt.
- Measure with the tool only (aggregates, opaque labels), after each fix merges; append one ledger row below.
- A gap that is the source's fault becomes a named source defect with its reason.
- L1 only (translates whole); no claim about L2+.
- Finish: 40 of 40 accounted (whole or named), time box 14 days from T0; publish the ledger as it stands at the time box.
Gap classes (owners)
- Bare LayoutError, 9 programs (#7644; some may be source defects) (#7714)
- No such item, 3 programs (no owner yet) (#7730)
- Bytes overlap COMP-1/2/5, 3 programs (#7646 slice 5): flip
translate()to defaultzos_comp5=True(owner ruling B, 2026-11-04; the v2.12.1 hold was lifted by the owner 2026-11-05, no release pending). Regenerate the affected goldens and re-prove the 5 burned COMP-5 programs (CardDemo PAUDBLOD / PAUDBUNL / DBUNLDGS, async ASYNCPNT / SEQPNT), then re-survey. - STRING numeric sender with P or a decimal place, 2 programs (#7523). Re-opened 2026-11-05: #7738 named the wide literal a hole, but T3 still shows this gap. (#7752) Re-opened again 2026-11-05 evening: no PR since T3 closed this gap.
- EXEC CICS map: no such field, 2 programs (#4270)
- JSON GENERATE / PARSE, 2 programs (#7524)
- Code-page literals (MOVE, STRING, UNSTRING / INSPECT beyond the single-byte code page), consolidated in #7526. T3: MOVE 2 programs, STRING 1. #7738 names the wide-literal hole.
- EXEC CICS WEB CONVERSE / RECEIVE / HTTPHEADER, 1 program (#7525)
- EXEC SQL ROLLBACK in CICS, 1 program (#7527) (#7727; the row is gone at T3)
- Tool: gap_prevalence names closed #4767 as the owner of the census EXEC CICS WEB rows. Point them at #7525 (one-line owner-map fix). (#7754)
- Tool:
cics_census.py blockers --unmaskprints census repository and program names in its per-program rows. Scrub them as gap_prevalence's census half does (protocol rule 2). (#7755)
Ledger (one row per re-survey)
| date | main | whole / 40 | gap closed (PRs) | predicted vs actual | new gaps exposed | cost (PRs, worker-h, $) | named, not fixed |
|---|---|---|---|---|---|---|---|
| 2026-10-24 | 6758295f2 | 8 | baseline | - | - | - | - |
Related: #6064 (no current non-burned translation rate), #5865 (coverage-if-closed never validated against a run), #3803 (the real blind trial this rehearses).
- 主要言語
- Python
- スター
- 57
- フォーク
- 11
- 平均マージ
- 1時間 32分
- マージ済み PR(30日)
- 974
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
squid-protocol/gitgalaxy のほかの issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 72/100
squid-protocol/gitgalaxy#7811 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 47/100
squid-protocol/gitgalaxy#7813 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
enhancement legacy-modernization priority: medium scope:frontier
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
squid-protocol/gitgalaxy#7646 · コメント 15 件 ·
メンテナーはふだん 1 日以内に返信
-
documentation
難易度 3/5 1〜2日 初心者へのやさしさ 68/100
squid-protocol/gitgalaxy#7628 ·
メンテナーはふだん 1 日以内に返信
-
documentation epic
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
squid-protocol/gitgalaxy#7624 ·
メンテナーはふだん 1 日以内に返信
squid-protocol/gitgalaxy の issue をすべて見る
似ている issue
-
request-theme
難易度 1/5 1時間未満 初心者へのやさしさ 78/100
LizardByte/ThemerrDB#9883 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
Project-MONAI/MONAI#9258 ·
メンテナーはふだん 3 日以内に返信
-
catalog:deprecation
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
surendranb/free-inference#31 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
fritzprix/libr-agent#2612 ·
メンテナーはふだん 1 日以内に返信
-
needs-triage presubmit-gate
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
gke-labs/kube-agents#5001 ·
メンテナーはふだん 1 日以内に返信