determinism: a daemon pause that cannot engage gives different traces across runs (intermittent, added by #73)
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
- Tech stack
- javascript, typescript
- 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
- 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