random seed: generated finds a greppable-stream counterexample on main too: stdout has 189 gap lines for 190 gaps (seed 333199054)
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 30/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- javascript, node.js
研究方向
Start in packages/oracles with the issue's replay command, using --config oracle-gaps/vitest.config.mjs gap-report-oracle; the failing unit is oracle-gaps.report / random seed: generated with seed 333199054 and path 1:1:1:1. Read the gap-report oracle and CLI stream writer to see how gaps are counted versus printed, and where the framework builds its Replay line. Done means the seed reproduces the 189-vs-190 mismatch and both the missing gap line and incorrect replay command are located.
由索引模型根據 Issue 內容生成。
描述
Summary
The end-to-end gap oracle's random unit random seed: generated found a counterexample in CI: at checkpoint cli, the greppable stream law fails with "the stdout has 189 gap lines for 190 gaps". The base fails the same way, so this is not caused by PR #90. Filed as an issue under P4, not rerun away.
- CI: run 43688703700 (head 082991d), job
Gap report end-to-end oracle (random seed, 3/3). The seed was 333199054, path1:1:1:1. - Replays, each run twice with the same seed and path: on
origin/main(5726197), 1 gap line short both times; on PR head 7df4a50, the same.
Replay
cd packages/oracles && ORACLE_SEED=333199054 ORACLE_PATH=1:1:1:1 ORACLE_PROPERTY=oracle-gaps.report ORACLE_UNIT='random seed: generated' pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "^oracle-gaps\.report(?: | > )random seed: generated$"
The counterexample history is printed in the failure message (History: {...}).
Two defects in the report
- The printed Replay line does not reproduce this unit. The framework prints
ORACLE_SEED=... ORACLE_PATH=... ORACLE_PROPERTY=... ORACLE_UNIT=... vitest run -t '...'. In this package, a barevitest runuses the default config and finds no file: all 173 tests are skipped. The command needs--config oracle-gaps/vitest.config.mjs gap-report-oracle. The framework should print the project's test command, or this package's replay should say so. - The stream lost one gap line. The stdout has one fewer gap line than the gaps reported. The cause is not known. Related but not the same: #87 (Windows, one extra line), and #76 (an intermittent stop with results missing beside the stream log).
Cost
The unit spent 817 s in this failing run, mostly in shrinking, and the job took 14 minutes. That is over the 10-minute budget (P12). A counterexample shrinks through up to six histories, and each one runs the real CLI.
Authority
P4 (register): a counterexample is filed as an issue with its replay line, and a rerun never hides it. Under the M phase-1 decision, a random counterexample that the base also fails is filed, not blocking. The determinism-as-main reading in PR #90 applies the same rule to determinism units. The greppable-stream law (maintainer request 2026-11-12) is the one that fails.
- 主要語言
- JavaScript
- 星號
- 5
- 分支
- 1
- 平均合併
- 8 小時 31 分鐘
- 30 天內合併 PR
- 60
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
TanStack/oracles 的其他 Issue
-
難度 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 天內回覆
-
難度 5/5 一週以上 新手友好度 35/100
維護者通常 1 天內回覆
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 82/100
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
channels:edit check:passed
難度 2/5 1-3 小時 新手友好度 65/100
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 84/100
swc-project/swc-next-issues#490 ·
-
feedback simulation workshop
難度 2/5 1-3 小時 新手友好度 69/100
githubnext/gh-aw-workshop#5826 ·
維護者通常 1 天內回覆