determinism: constructed history: an edit sequence through the daemon fails on main; excluded from PR CI until fixed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript, nodejs
- Domain
- testing-qa
Research direction
Start by reproducing with the replay command inside packages/oracles: pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "determinism: constructed history: an edit sequence through the daemon", and record the printed History: {...} from repeated runs to see where the test-output daemon stream note appears in one trace but not the other. Read the oracle-gaps vitest config and the gap-report-oracle unit to find how the daemon stream note is captured, then trace back into #92 for prior context. Done means the two runs of one constructed history produce identical traces and the unit is removed from the excluded list for the oracle-gaps-determinism partition in packages/oracles/scripts/pr-shards.mjs.
Written by the indexing model from the issue text.
Description
Summary
determinism: constructed history: an edit sequence through the daemon fails on main (35422e3, and the control run at 5726197 for the units it lists there). Its two runs of one history record different traces. Root cause: a daemon stream note (the test-output note) appears in one run and not the other; the cause is not yet determined. Tracked in #92.
Excluded from PR CI by PR #90 (the oracle-gaps-determinism partition's excluded list in packages/oracles/scripts/pr-shards.mjs). Removal condition: the fix lands and the unit is taken off that list, so PR CI runs it again.
Replay
cd packages/oracles && pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "determinism: constructed history: an edit sequence through the daemon"
The failure message prints the history (History: {...}). Determinism units have no Replay: line.
- 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