random seed: a declaration fault: brokenOwner: a drawn history does not enter 'blocked by brokenOwner' (seed -1269403528), on main too

Open
#107 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
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
testing

Research direction

Start in packages/oracles and run the Replay command with ORACLE_SEED=-1269403528 ORACLE_PATH=0 ORACLE_PROPERTY=oracle-gaps.report, adding the --config oracle-gaps/vitest.config.mjs gap-report-oracle that the printed Replay line drops (#102). Read the gap-report-oracle property to see how the brokenOwner history is drawn and where the blocked by brokenOwner state should be entered. Done means the drawn history reaches that state, or the open question — whether every drawn brokenOwner history must — is settled and encoded there.

Written by the indexing model from the issue text.

Description

Summary

The random unit random seed: a declaration fault: brokenOwner found a counterexample in CI on PR #90 (head cd8e0f9, job Gap report end-to-end oracle (random seed, 3/3), run 43701076084): the drawn history did not enter the state blocked by brokenOwner. The constructed history must reach every state it names.

It reproduces with the same seed and path on origin/main (4d3c8a9, twice) and on the PR head (twice), so the base has it. Under the M phase-1 rule it is filed, not blocking. Filed under P4; not rerun away.

Replay

cd packages/oracles && ORACLE_SEED=-1269403528 ORACLE_PATH=0 ORACLE_PROPERTY=oracle-gaps.report ORACLE_UNIT='random seed: a declaration fault: brokenOwner' pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "^oracle-gaps\.report(?: | > )random seed: a declaration fault: brokenOwner$"

The Replay line the framework prints omits --config oracle-gaps/vitest.config.mjs gap-report-oracle, so it does not run here either (#102).

Open questions

Whether the state should be reached by every drawn brokenOwner history, or only by the constructed one. The drawn history may not reach the blocking step under this seed (the blocked state needs an owner that the drawn history leaves out). A decision on the law, not only on the drawn data, is needed.

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.