Windows e2e: stdout has one more gap line than the expected count (fixed seed 4/10, noTypescript)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- testing
Research direction
Start from the failing Windows job log for fixed seed 20261105: a declaration fault: noTypescript and compare the 169 oracle-gaps: stdout lines against the expected 168 gaps to isolate the extra line. Then trace where that checkpoint emits gap lines in the e2e harness, using the earlier #73 Windows stdout-count fix as the closest precedent. Done means the fixed-seed Windows run reports exactly 168 lines and the source of the extra line is explained.
Written by the indexing model from the issue text.
Description
Job: https://github.com/TanStack/oracles/actions/runs/43661845394/job/132652674703 (Windows gap report end-to-end oracle, fixed seed 4/10, on #73 at 104376d)
Test: fixed seed 20261105: a declaration fault: noTypescript (9.0 min on windows-latest)
Error:
oracle-gaps.report violated at checkpoint "stdout" (law: greppable stream).
Difference: the stdout has 169 gap lines for 168 gaps: ["oracle-gaps: gap not-distinguished L4 sut.ts:M1 ` process.env.NODE_ENV !== 'production' ` → ` undefined `", "oracle-gaps: gap not-observed L4 sut.ts:M2 ` !== ` → ` === `", "oracle-gaps: gap unreached L6 sut.ts:M3 ` false ` → ` undefined `", ...]
What this is: the stdout of the run has one more gap line than the expected count of gaps, on win32. It is the same family as the earlier Windows stdout-count breach (fixed on #73 for authored mutants). The extra line has not been identified; the full list of 169 lines is in the failing run's log.
Not: the oracle's expected count for this history. Linux runs pass.
Found while reviewing #73 (its body links this issue). Non-blocking: Windows end-to-end is non-blocking under C entry (c) until #79.
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 1
- Avg merge
- 6h
- Merged PRs (30d)
- 56
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 TanStack/oracles
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TanStack/oracles#120 · 1 comment ·
Maintainers usually reply within 1 day
-
windows
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TanStack/oracles#118 · 1 comment ·
Maintainers usually reply within 1 day
All issues in TanStack/oracles
Similar issues
-
Edit: Telemante [YT]Openchannels:edit check:passed
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
fix
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
idean3885/claude-ops-agent#1083 ·
Maintainers usually reply within 1 day
-
入群码过期Open
Difficulty 1/5 Under an hour Newbie friendliness 84/100
aliyun/ai-agent-handbook#29 · 1 comment ·
-
docs documentation need-triage SaaS
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
apache/cloudstack#14719 ·
Maintainers usually reply within 1 day