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 摘要。