determinism: an edit sequence through the daemon records a test-output note in one run and not the other

Open
#92 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@KyleAMathews is already working on this.

Since Nov 16, 2026.

  • #126 by @KyleAMathews — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
testing

Research direction

Start by running the replay from 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". Read the determinism unit and the daemon-stream note emission path around oracle-gaps to find where the test-output.log note is appended. Diff full traces at the incremental checkpoint rather than the truncated prefix. Done means two runs record the same trace, or the comparison excludes that note with a stated reason in the coverage map.

Written by the indexing model from the issue text.

Description

Summary

The determinism unit determinism: constructed history: an edit sequence through the daemon fails on main (35422e3). Two runs of the same history differ in one daemon stream note: one run's stream includes oracle-gaps: note test output in <package>/<out>/test-output.log, and the other's does not. Found by the determinism units that CI-1 moves onto pull requests (PR #90).

Evidence

Structural diff of the two full traces (a scratch patch printed the untruncated texts), at checkpoint incremental:

  • $.daemon.stream.notes.1 exists in one run only. Both runs share --hang-limit 20000 ms is above --mutant-limit 15000 ms ... as note 0.

The cause is not determined. The note appears when a test's output is captured, so it probably depends on a timing race between the daemon's test output and the check's end. That has not been confirmed.

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"

Notes

The 2,000-character prefix in the determinism message (#81) hid this difference. A diff needed the full texts. The check's law is that two runs of one history record the same trace, so either the note must be deterministic, or the comparison must leave it out with a stated reason in the coverage map.

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.