determinism: the CLI's heartbeat list depends on wall-clock timing, so five determinism units fail on main

未關閉
#91 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

@KyleAMathews 已經在處理了。

開始於 2026年11月15日。

  • #90 來自 @KyleAMathews —— 未關閉

評估

難度
4/5
預估耗時
3-5 天
新手友好度
22/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
javascript, typescript
領域
testing

研究方向

Start by reproducing one failing unit with the command given: cd packages/oracles && pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "determinism: constructed history: a declaration fault: brokenOwner", and read the History: {...} payload plus the structural diff against $.heartbeats. Then read the determinism units themselves and the CLI heartbeat recording code they exercise, alongside the related issue #84, to see where wall-clock ordering enters. Done means the five listed units pass reliably, but the fix path (excluding the heartbeat set from comparison versus a test-only pause point) is undecided and needs a maintainer call first.

由索引模型根據 Issue 內容生成。

描述

Summary

Five determinism units of the end-to-end gap oracle fail on main (35422e3). Each one runs a history twice and compares the two traces. The traces differ in the CLI's heartbeats list, which records which busy mutants beat. Whether a mutant beats depends on wall-clock timing, so the comparison is timing-dependent. Found by the determinism units that CI-1 moves onto pull requests (PR #90).

Failing units (main 35422e3, one Arclet, one Vitest worker)

  • determinism: constructed history: an edit sequence over the witness module
  • determinism: constructed history: every outcome class
  • determinism: constructed history: a declaration fault: brokenOwner
  • determinism: constructed history: a declaration fault: noTypescript
  • determinism: generated 2

Evidence

Each failure is at observation 0 (cli). A structural diff of the two full traces (captured with a scratch patch that prints the untruncated texts, since the message keeps 2,000 characters) differs only in $.heartbeats. For brokenOwner, one run's list includes sut.ts:M177 and the other's does not. The other units show the same kind of shift in the list.

Replay

Determinism units have no replay line. Run one unit with the project's command:

cd packages/oracles && pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "determinism: constructed history: a declaration fault: brokenOwner"

The history is printed in the failure message (History: {...}).

Why it matters

The register's "determinism under load" decision (2026-11-13) says that an oracle driver must not rely on wall-clock ordering. This comparison records a timing-dependent set, so it fails under load even when the CLI is deterministic. #84 is the reach side of the same timing (the heartbeat state's count per shard). This issue is the determinism side.

Open question for the maintainer

Either the determinism comparison should leave the heartbeat set out, since "each beat is observed as its mutant and file, not how long or how often it beat" (the law's own wording), or the beat set should be made deterministic through a test-only pause point as in #84's proposed fix. Not decided here.

主要語言
JavaScript
星號
5
分支
1
平均合併
8 小時 31 分鐘
30 天內合併 PR
60

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TanStack/oracles 的其他 Issue

查看 TanStack/oracles 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。