constructed-order.json is a stale prefix: 19 constructed histories are unrecorded

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
领域
testing

调研方向

Read packages/oracles/oracle-gaps/constructed-order.json and the canary in packages/oracles/tests/gap-report-history-fingerprint.test.ts. Compare the recorded 90 names with the 109 current constructed histories using the fixed seed 20261105, then update the list and canary to catch missing entries. Done means the recorded order includes all histories and the test fails if a history is omitted or inserted before a recorded one.

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

描述

packages/oracles/oracle-gaps/constructed-order.json is a stale prefix of the constructed histories of the gap e2e oracle. The canary appends new constructed histories, and never inserts one before a recorded one (packages/oracles/tests/gap-report-history-fingerprint.test.ts) only checks that the recorded list is a prefix of the current list, so the 19 missing names are not caught.

Measured at 11d5aa3d (plus the #182 fix on top, which adds the last one):

  • current constructed histories (fixed seed 20261105 units): 109
  • recorded in constructed-order.json: 90 (a valid prefix)
  • missing: 19

Missing names, in current order:

  • a slow owner's kill and another owner's kill
  • a backstop cut ends the copies ahead of a later kill
  • a kill past the work budget in a later owner
  • a slow kill after a 16 s wait
  • a copy waiting on a timer
  • a copy waiting on an unref'd timer
  • a copy waiting on a pipe it opened
  • a copy beside the runner's pending write
  • a copy beside the runner's pending timer
  • a clocked copy that spins
  • an authored mutant whose owner hangs
  • a stream log lost after its note, then stopped, unsupervised
  • a heavy test that reads the clock after its work
  • a heavy test that reads the clock first
  • a hang in a file whose test does a short read
  • a clocked owner beside a counted one under the work budget
  • a spin after a short async read
  • an authored mutant whose owner spins
  • a later owner's test listed first beside an earlier owner's hang (added by #182)

Proposed fix: record all 109 names in order, and make the canary also require the recorded list to equal the current list for every name that existed on main (or require exact equality on each PR that adds a history). The file is #99's to own once #99 merges; this issue exists so the stale state is visible and tracked rather than left silent.

主要语言
JavaScript
星标
5
派生
1
平均合并
11 小时 18 分钟
30 天内合并 PR
66

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TanStack/oracles 的其他 Issue

查看 TanStack/oracles 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。