René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"determinism: an edit sequence through the daemon records a test-output note in one run and not the other","articleBody":"## Summary\n\nThe 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 \u003cpackage>/\u003cout>/test-output.log`, and the other's does not. Found by the determinism units that CI-1 moves onto pull requests (PR #90).\n\n## Evidence\n\nStructural diff of the two full traces (a scratch patch printed the untruncated texts), at checkpoint `incremental`:\n\n- `$.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.\n\nThe 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.\n\n## Replay\n\n    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\"\n\n## Notes\n\nThe 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.\n","author":{"url":"https://github.com/KyleAMathews","@type":"Person","name":"KyleAMathews"},"datePublished":"2026-11-15T04:55:12Z","url":"https://github.com/TanStack/oracles/issues/92"}