determinism: an edit sequence through the daemon records a test-output note in one run and not the other

未关闭
#92 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@KyleAMathews 已经在做这个了。

开始于 2026年11月16日。

  • #126 来自 @KyleAMathews —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript
领域
testing

调研方向

Start by running the replay from packages/oracles: pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "determinism: constructed history: an edit sequence through the daemon". Read the determinism unit and the daemon-stream note emission path around oracle-gaps to find where the test-output.log note is appended. Diff full traces at the incremental checkpoint rather than the truncated prefix. Done means two runs record the same trace, or the comparison excludes that note with a stated reason in the coverage map.

由索引模型根据 Issue 内容生成。

描述

Summary

The determinism unit determinism: constructed history: an edit sequence through the daemon fails on main (35422e3). Two runs of the same history differ in one daemon stream note: one run's stream includes oracle-gaps: note test output in <package>/<out>/test-output.log, and the other's does not. Found by the determinism units that CI-1 moves onto pull requests (PR #90).

Evidence

Structural diff of the two full traces (a scratch patch printed the untruncated texts), at checkpoint incremental:

  • $.daemon.stream.notes.1 exists in one run only. Both runs share --hang-limit 20000 ms is above --mutant-limit 15000 ms ... as note 0.

The cause is not determined. The note appears when a test's output is captured, so it probably depends on a timing race between the daemon's test output and the check's end. That has not been confirmed.

Replay

cd packages/oracles && pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "determinism: constructed history: an edit sequence through the daemon"

Notes

The 2,000-character prefix in the determinism message (#81) hid this difference. A diff needed the full texts. The check's law is that two runs of one history record the same trace, so either the note must be deterministic, or the comparison must leave it out with a stated reason in the coverage map.

主要语言
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 摘要。