determinism: a daemon pause that cannot engage gives different traces across runs (intermittent, added by #73)

Open
#105 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
28/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
testing

Research direction

Start by reproducing from packages/oracles with the given pnpm exec vitest command against oracle-gaps/vitest.config.mjs, and read the failing test for determinism: constructed history: a daemon pause that cannot engage to see how the history is constructed. Then read src/oracle-property.ts, where the failure message and trace printing live, and compare two runs' traces at the reported observation to find where wall-clock timing leaks in. Done means the history produces identical traces across repeated runs and the test is re-enabled in PR CI. This is an intermittent ordering bug needing familiarity with the oracle driver, so pair with a maintainer.

Written by the indexing model from the issue text.

Description

Summary

The determinism unit determinism: constructed history: a daemon pause that cannot engage (added to main by #73) is intermittent. Two runs of one history recorded different traces at observation 4 (incremental). It passed on one run and failed on another for the same commit (4bc4eb1, PR #90). It also failed on main (4d3c8a9) before the stream-order fix, at observation 0 (cli).

PR #90 excludes it from PR CI until this is fixed, so the determinism job is not red at random.

Replay

cd packages/oracles && pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "determinism: constructed history: a daemon pause that cannot engage"

The failure message prints the history and the first 2,000 characters of each run's trace. For the full texts, a scratch patch to src/oracle-property.ts that prints them was needed (see #81).

Authority

Register (2026-11-14, determinism under load): an oracle driver must not rely on wall-clock ordering. A daemon pause that depends on timing is that kind of dependency.

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.