cobolrt exit route: record which COBOL quirks fire in production so customers can safely simplify the Java
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- java
- Domain
- observability, tooling
Research direction
The payload names no files, only the cobolrt runtime and its catalogue rule IDs, so locate where quirk paths such as truncation, non-digit reads, binary wrap and low-values comparison are handled and where rule IDs are attached. Telemetry must be off by default with measured overhead, and the simplification report needs a defined format and a worked example. Done means the epic's acceptance criteria are met and a PROVED example still passes.
Written by the indexing model from the issue text.
Description
Owner-approved (2026-10-08): offer customers an exit route instead of lock-in.
What. Optional, low-overhead telemetry in cobolrt that records which quirk paths, keyed by catalogue rule ID, actually execute. Examples: intermediate truncation changed a value; a non-digit was read; a binary item wrapped; low-values were compared.
From that, generate a per-program simplification report: places where the COBOL semantics never mattered in production and a runtime call can be replaced by plain Java (BigDecimal/int arithmetic, String compares). Each suggestion comes with the evidence behind it and a test to keep.
Acceptance.
- Telemetry off by default, with measured overhead when on.
- A report format.
- A worked example on one burned-estate program: a suggested simplification applied, still PROVED, and readability improved.
- Docs for customers.
Part of the cobolrt-as-a-product epic (linked from the epic). Owner-approved direction, 2026-10-08.
🤖 Generated with Claude Code
- 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
-
docs size:S
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
strawberry-graphql/strawberry#4794 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dataforgoodfr/cetolog#21 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
btclib-org/btclib#2932 ·
Maintainers usually reply within 1 day