consumer_acceptance: a same-path rerun after a floor refusal lowers the recorded inventory floor
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- testing-qa
Research direction
Run timeout 40s python3 /tmp/critic-ca3/repro_floor_persistence.py to reproduce the repeated-run failure, then inspect the consumer_acceptance harness's same-path record handling. Verify that two runs against the two-consumer ecosystem both fail with the missing consumer named, and that the harness self-test catches a planted fault.
Written by the indexing model from the issue text.
Description
Found by the blind critic on the #1275 consumer_acceptance shrink (round 3, c98a743). It is pre-existing: the old harness at 88ba928 fails the same repeated-run check.
Problem. Start from a dated COMPLETE record with 3 rows, and a current ecosystem with only 2 consumers. Run 1 correctly refuses (record_floor=3). It then writes its own record at the SAME path with inventory=2. Run 2 reads only that smaller record and PASSes. The historical floor is lost after one unsuccessful run.
Reproduce (dev box): timeout 40s python3 /tmp/critic-ca3/repro_floor_persistence.py <harness>.
Done when:
- The floor a refusing run writes is the max of the prior floor and its own inventory, and the missing consumer's name is carried forward.
- Two consecutive runs against the 2-consumer ecosystem both FAIL naming the missing consumer.
- A planted fault in the harness self-test covers it.
- Dominant language
- C
- Stars
- 3
- Forks
- 7
- Avg merge
- 3h 56m
- Merged PRs (30d)
- 102
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a 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 InauguralSystems/EigenScript
-
area:lint-tooling bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
InauguralSystems/EigenScript#1340 ·
Maintainers usually reply within 1 day
-
area:stdlib found-by:code-review kind:silent-wrong
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
InauguralSystems/EigenScript#1338 ·
Maintainers usually reply within 1 day
-
area:lint-tooling found-by:critic kind:docs-drift
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
InauguralSystems/EigenScript#1335 ·
Maintainers usually reply within 1 day
-
area:ci found-by:critic kind:gate-defect
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
InauguralSystems/EigenScript#1311 ·
Maintainers usually reply within 1 day
-
enrolment: decide test_gc_runner_controls.py (exempt vs enrol) and whether floors need a ratchetOpenarea:gates found-by:critic kind:decision
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
InauguralSystems/EigenScript#1280 · 1 comment ·
Maintainers usually reply within 1 day
All issues in InauguralSystems/EigenScript
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
johnsonjh/emu2-cpm86#68 · 1 comment ·
Maintainers usually reply within 1 day
-
Zenmap CrashOpenZenmap
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
fastfetch-cli/fastfetch#2619 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Template: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
betaflight/betaflight#15759 ·
Maintainers usually reply within 1 day