det_mutation: an evidence refresh raced a full run; #7476's verdicts have no attack on record
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- testing-qa
Research direction
The stale evidence comes from a refresh cut from an older commit than #7460, and the affected ledgers are the survivors files for cbsa-abndproc and cbsa-updcust. The batch verdicts for carddemo-sort-combtran and carddemo-sort-tranrept need survivor_attack.py try or strengthen.py to handle batch cases, which the payload says is not yet supported. Done means full re-runs of both ledgers and attack records for those 77 verdicts, but this needs project familiarity with the mutation pipeline.
Written by the indexing model from the issue text.
Description
- Evidence refresh #7428 was cut from a commit older than #7460, so it wrote samples over full runs:
cbsa-abndprocwent from 455 of 455 mutants to 149, andcbsa-updcustfrom 718 of 718 to 148. The survivors files still list all 307 and 385, and both programs stay L5 on fewer mutants judged. #7482 now fails a run narrower than the one it replaces, so this cannot recur unseen. The two ledgers still need a full re-run. - #7476 merged 77 new
equivalent/unreachableverdicts oncarddemo-sort-combtranandcarddemo-sort-tranreptwith no attack on record. Both are batch cases, whichsurvivor_attack.py trydoes not handle yet, so they need that support orstrengthen.pybefore those verdicts mean anything.
- 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