determinism: constructed history: an edit sequence through the daemon fails on main; excluded from PR CI until fixed

Open
#98 0 comments 0 reactions 0 assignees View on GitHub

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TanStack/oracles

All issues in TanStack/oracles

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.