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

未关闭
#2,436 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
52/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
testing-qa

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
TypeScript
星标
4k
派生
286
平均合并
1 天 1 小时
30 天内合并 PR
104

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TanStack/db 的其他 Issue

查看 TanStack/db 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。