determinism: constructed history: an edit sequence through the daemon fails on main; excluded from PR CI until fixed

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
javascript, nodejs
领域
testing-qa

调研方向

Start by reproducing with the replay command inside 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", and record the printed History: {...} from repeated runs to see where the test-output daemon stream note appears in one trace but not the other. Read the oracle-gaps vitest config and the gap-report-oracle unit to find how the daemon stream note is captured, then trace back into #92 for prior context. Done means the two runs of one constructed history produce identical traces and the unit is removed from the excluded list for the oracle-gaps-determinism partition in packages/oracles/scripts/pr-shards.mjs.

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

描述

Summary

determinism: constructed history: an edit sequence through the daemon fails on main (35422e3, and the control run at 5726197 for the units it lists there). Its two runs of one history record different traces. Root cause: a daemon stream note (the test-output note) appears in one run and not the other; the cause is not yet determined. Tracked in #92.

Excluded from PR CI by PR #90 (the oracle-gaps-determinism partition's excluded list in packages/oracles/scripts/pr-shards.mjs). Removal condition: the fix lands and the unit is taken off that list, so PR CI runs it again.

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"

The failure message prints the history (History: {...}). Determinism units have no Replay: line.

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