Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Calls] Preserve complete symbolic exceptional observations for class replay diagnostics

未关闭
#497 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
8/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
java, kotlin
领域
testing-qa

调研方向

This is internal symbolic-execution work in the usvm engine with a frozen experiment ledger and multiple gating contracts, so it is not a starting point for a first contribution. The payload names the sealed ledger selection-ledger-v7.json and V7_INFRASTRUCTURE_FRONTIER.md, which must not be overwritten. Done would mean exceptional observations match the exact native outcome, which the issue leaves to the maintainers to define.

由索引模型根据 Issue 内容生成。

描述

Part of https://github.com/UnitTestBot/usvm/issues/483.

Observed boundary

Priority: P2. strict symbolic observation gap; native primary coverage already fixed in MR #479.

The original EMPTY_FRESH HashMap reproduction had five symbolic THREW candidates with incomplete strict snapshots; their native coverage was real.

Implementation scope

Provide comparable bounded exceptional observations for symbolic class scenarios: actual thrown kind/value and observable receiver state/effects at the throw point, including constructor failure. Reuse native error/value snapshots and existing engine catch semantics. Suspended prefixes must remain input-only and never acquire an invented terminal observation.

Acceptance criteria

  • Source cases throwing a primitive or modeled Error retain the observable state/effects and compare against the exact native outcome.
  • Constructor failures distinguish an unavailable external receiver from an incomplete observation; no invented successful construction.
  • Strict applicability/rejection is separate from complete agreeing native coverage. This work must not restore the old gate that discarded genuine native coverage on symbolic mismatch.

Existing work to reuse or coordinate

Evidence and delivery rules

Use the frozen v7 200-class ledger and the source-linked reproducer; do not overwrite sealed experiment output. Reuse existing loaders, domain projection, source instrumentation, candidate/replay contracts and bounded observations. Keep original class members and independently frozen domain policies. Run focused source/native checks for the changed contract and leave broad suites to CI; unsupported and newly exposed later gates remain recorded.

Local evidence: iccq2026-paper/experiments/class-coverage-round-robin-20261002/real-class-campaign-20261014/{original/selection-ledger-v7.json,V7_INFRASTRUCTURE_FRONTIER.md} and real-class-machine-diagnostic-20261014/revised-protocol-v8/README.md.

主要语言
Kotlin
星标
33
派生
27
平均合并
3 天 21 小时
30 天内合并 PR
88

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

UnitTestBot/usvm 的其他 Issue

查看 UnitTestBot/usvm 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。