query.scope-omission-reacquisition (chromium-opfs): nondeterministic trace at opfsCleanupRetry

Open
#2,436 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
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
testing-qa

Research direction

Start with e2e/query-scope-omission-oracle.browser.test.ts and the adapter-oracles-chromium project; reproduce the reported chromium-opfs trace mismatch at opfsCleanupRetry. Then trace how the browser driver records that observation and compare the two runs. Done means the cause is addressed by making retry observation deterministic or excluding the retry count, with the choice recorded oracle-first.

Written by the indexing model from the issue text.

Description

A browser oracle recorded different traces on two runs of the same history on PR #2432's CI. #2432 changes only scripts/lint-scope-oracle.property.test.js, so this nondeterminism is on main.

  • Job: E2E (adapter-browser), job 131624497770
  • File: e2e/query-scope-omission-oracle.browser.test.ts (project adapter-oracles-chromium): 1 failed, 786 passed
  • Error: query.scope-omission-reacquisition.chromium-opfs: two runs of "generated 1" recorded different traces at observation 14 ("opfsCleanupRetry").

A determinism unit that fails means the run depends on something besides its history. Here the likely cause is the timing of OPFS cleanup retries. Either the driver must make the retry observation deterministic (for example, with a controlled clock or a fixed retry schedule), or the observation must leave out the retry count. Record which, oracle-first.

This issue was written by Isaac.

Dominant language
TypeScript
Stars
4k
Forks
286
Avg merge
1d 1h
Merged PRs (30d)
104

Getting set up

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/db

All issues in TanStack/db

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.