det: JSON GENERATE / JSON PARSE not modelled (census #7709, 2 programs)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
Research direction
The survey lives in cics_census.py, run as survey --out DIR --label before with CICS_CENSUS_CORPORA set, then blockers DIR --label before reports the gap. The issue gives no file or test for the JSON GENERATE/PARSE translator, so first find where the det translator handles statement families and how it marks one as not modelled. Done would mean the census reports these statements as modelled, but the issue does not define that criterion or name a burned-estate corpus to check against.
Written by the indexing model from the issue text.
Description
Census breadth survey (#5052, main d86d5eabb): 2 non-burned CICS programs (of 21 surveyed) hit this gap, counts only; no census code was read (mainframe-evidence-policy 3).
Gap family: JSON GENERATE / JSON PARSE
Det translator status: not modelled / refused. Burned-estate programs affected: 0. None of these alone makes a non-burned program whole (other gap classes remain), so rank by program count only.
Class / Sibling gaps
Class: det-translator statement families the census surveys report as "not modelled" in CICS programs. Siblings are the other rows in the #5052 ranking comment (STRING, JSON GENERATE/PARSE, EXEC CICS WEB, MOVE single-byte literal, EXEC SQL ROLLBACK in CICS); each has its own issue. Work only from burned estates (case work on non-burned repos is out of scope).
Reproduce: cics_census.py survey --out DIR --label before with CICS_CENSUS_CORPORA, then blockers DIR --label before.
Slices (census #7709, owner reopen 2026-11-05)
Work from IBM's definition on fixtures / cics-crucible only; never census source (#7709 rule 2).
- JSON GENERATE: translate from the IBM definition (name matching, NAME / SUPPRESS / COUNT, JSON-CODE, ON EXCEPTION) on a fixture; register entry marks it oracle-unbacked (no L2+ claim)
- JSON PARSE: same, on a fixture (name matching, CONVERTING / WITH DETAIL, JSON-STATUS, ON EXCEPTION)
- Re-survey: the 2 census JSON rows are gone; post the count on #7709
- Dominant language
- Python
- Stars
- 57
- Forks
- 11
- Avg merge
- 1h 35m
- Merged PRs (30d)
- 975
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from squid-protocol/gitgalaxy
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
squid-protocol/gitgalaxy#7827 · 1 comment ·
Maintainers usually reply within 1 day
-
scope:frontier
Difficulty 5/5 Over a week Newbie friendliness 18/100
squid-protocol/gitgalaxy#7900 ·
Maintainers usually reply within 1 day
-
core-engine scope:infra testing
Difficulty 4/5 3-5 days Newbie friendliness 54/100
squid-protocol/gitgalaxy#7863 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
squid-protocol/gitgalaxy#7834 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 56/100
squid-protocol/gitgalaxy#7828 · 1 comment ·
Maintainers usually reply within 1 day
All issues in squid-protocol/gitgalaxy
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
graphql-python/graphql-core#304 ·
Maintainers usually reply within 1 day
-
docs size:S
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Gathin23/cleanyourtv#3464 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day