Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#497 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
8/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
java, kotlin
Domínio
testing-qa

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Kotlin
Estrelas
33
Forks
27
Merge médio
3d 21h
PRs com merge (30d)
88

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de UnitTestBot/usvm

Todas as issues de UnitTestBot/usvm

Issues semelhantes

Mais issues de Kotlin

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.