oracle-property: the History line is capped at 2000 characters, so a failing history cannot be filed in full
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 48/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- typescript
- 領域
- testing
研究方向
Start with packages/oracles/src/oracle-property.ts and inspect reportText plus the failure output that prints the History: and replay lines. Check how the framework handles histories that cannot be shrunk back, especially fixed, constructed entries, and canShrinkWithoutContext. Done means full histories are retained in CI output, replay output names the history being replayed, and the history replay gap is addressed here or tracked in a linked issue.
由索引模型根據 Issue 內容生成。
描述
reportText in packages/oracles/src/oracle-property.ts caps every printed value at 2,000 characters:
function reportText(value: unknown): string {
try {
return encodeData(value, ``, `report`).slice(0, 2000)
The History: line of a failing oracle uses reportText, so a failing history is truncated. The CI log for the #184 failure (run 44588135077, job "random seed, 3/4") cuts the history at 2,000 characters, so the full history cannot be recorded from CI.
Why it matters: M, "Replay by history" (register 2026-11-16) says a filed counterexample records its full history, not only its seed. Replay and base-replay attribution run that exact history. With this cap, the filed history for #184 (random seed: a daemon pause that cannot engage, seed -1120189360) is incomplete in CI output. A local scratch edit that removes the cap printed the full 3,593-byte history (83 keys), which is how #184 was captured.
Needed: print the full history in the failure (the cap removed, or a separate full-history line that the CI log keeps), and have the replay line name the history it replays. Separately, a history that the arbitrary cannot take back is rejected by fixed and by constructed entries (canShrinkWithoutContext is false), so a captured history cannot yet be replayed by history through the framework's own entries. That is a second gap for the same replay rule and should be covered here or in a linked issue.
Related: TanStack/oracles#184.
- 主要語言
- 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 天內回覆