constructed-order.json is a stale prefix: 19 constructed histories are unrecorded
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 55/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- javascript, node.js
- 領域
- testing
研究方向
Read packages/oracles/oracle-gaps/constructed-order.json and the canary in packages/oracles/tests/gap-report-history-fingerprint.test.ts. Compare the recorded 90 names with the 109 current constructed histories using the fixed seed 20261105, then update the list and canary to catch missing entries. Done means the recorded order includes all histories and the test fails if a history is omitted or inserted before a recorded one.
由索引模型根據 Issue 內容生成。
描述
packages/oracles/oracle-gaps/constructed-order.json is a stale prefix of the constructed histories of the gap e2e oracle. The canary appends new constructed histories, and never inserts one before a recorded one (packages/oracles/tests/gap-report-history-fingerprint.test.ts) only checks that the recorded list is a prefix of the current list, so the 19 missing names are not caught.
Measured at 11d5aa3d (plus the #182 fix on top, which adds the last one):
- current constructed histories (
fixed seed 20261105units): 109 - recorded in
constructed-order.json: 90 (a valid prefix) - missing: 19
Missing names, in current order:
- a slow owner's kill and another owner's kill
- a backstop cut ends the copies ahead of a later kill
- a kill past the work budget in a later owner
- a slow kill after a 16 s wait
- a copy waiting on a timer
- a copy waiting on an unref'd timer
- a copy waiting on a pipe it opened
- a copy beside the runner's pending write
- a copy beside the runner's pending timer
- a clocked copy that spins
- an authored mutant whose owner hangs
- a stream log lost after its note, then stopped, unsupervised
- a heavy test that reads the clock after its work
- a heavy test that reads the clock first
- a hang in a file whose test does a short read
- a clocked owner beside a counted one under the work budget
- a spin after a short async read
- an authored mutant whose owner spins
- a later owner's test listed first beside an earlier owner's hang (added by #182)
Proposed fix: record all 109 names in order, and make the canary also require the recorded list to equal the current list for every name that existed on main (or require exact equality on each PR that adds a history). The file is #99's to own once #99 merges; this issue exists so the stale state is visible and tracked rather than left silent.
- 主要語言
- JavaScript
- 星號
- 5
- 分支
- 1
- 平均合併
- 11 小時 18 分鐘
- 30 天內合併 PR
- 66
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
TanStack/oracles 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 64/100
維護者通常 1 天內回覆
-
難度 5/5 一週以上 新手友好度 25/100
維護者通常 1 天內回覆
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 78/100
fb55/htmlparser2#2579 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 66/100
維護者通常 1 天內回覆
-
needs verification
難度 2/5 1-3 小時 新手友好度 74/100
維護者通常 13 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 83/100
swc-project/swc-next-issues#532 ·
-
domain/checkout Platform(Default) priority/low testing/acceptance
難度 2/5 1-3 小時 新手友好度 76/100
維護者通常 1 天內回覆