cobolrt exit route: record which COBOL quirks fire in production so customers can safely simplify the Java
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 12/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- java
- 领域
- observability, tooling
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- 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
-
LLVM versions未关闭
难度 2/5 1-3 小时 新手友好度 67/100
维护者通常 1 天内回复
-
documentation good first issue language
难度 2/5 1-3 小时 新手友好度 91/100
-
good first issue help wanted translation
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
Fix duplicated word in speculative decoding docs可能已有人在做 @ddlw 今天认领。 未关闭community-request
难度 1/5 1 小时以内 新手友好度 89/100
NVIDIA/Megatron-LM#9118 ·
维护者通常 2 天内回复