random seed: generated finds a greppable-stream counterexample on main too: stdout has 189 gap lines for 190 gaps (seed 333199054)

オープン
#102 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
30/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
javascript, node.js
領域
cli, testing

調査の方向性

Start in packages/oracles with the issue's replay command, using --config oracle-gaps/vitest.config.mjs gap-report-oracle; the failing unit is oracle-gaps.report / random seed: generated with seed 333199054 and path 1:1:1:1. Read the gap-report oracle and CLI stream writer to see how gaps are counted versus printed, and where the framework builds its Replay line. Done means the seed reproduces the 189-vs-190 mismatch and both the missing gap line and incorrect replay command are located.

索引モデルが issue の本文から書いたものです。

説明

Summary

The end-to-end gap oracle's random unit random seed: generated found a counterexample in CI: at checkpoint cli, the greppable stream law fails with "the stdout has 189 gap lines for 190 gaps". The base fails the same way, so this is not caused by PR #90. Filed as an issue under P4, not rerun away.

  • CI: run 43688703700 (head 082991d), job Gap report end-to-end oracle (random seed, 3/3). The seed was 333199054, path 1:1:1:1.
  • Replays, each run twice with the same seed and path: on origin/main (5726197), 1 gap line short both times; on PR head 7df4a50, the same.

Replay

cd packages/oracles && ORACLE_SEED=333199054 ORACLE_PATH=1:1:1:1 ORACLE_PROPERTY=oracle-gaps.report ORACLE_UNIT='random seed: generated' pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "^oracle-gaps\.report(?: | > )random seed: generated$"

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

Two defects in the report

  1. The printed Replay line does not reproduce this unit. The framework prints ORACLE_SEED=... ORACLE_PATH=... ORACLE_PROPERTY=... ORACLE_UNIT=... vitest run -t '...'. In this package, a bare vitest run uses the default config and finds no file: all 173 tests are skipped. The command needs --config oracle-gaps/vitest.config.mjs gap-report-oracle. The framework should print the project's test command, or this package's replay should say so.
  2. The stream lost one gap line. The stdout has one fewer gap line than the gaps reported. The cause is not known. Related but not the same: #87 (Windows, one extra line), and #76 (an intermittent stop with results missing beside the stream log).

Cost

The unit spent 817 s in this failing run, mostly in shrinking, and the job took 14 minutes. That is over the 10-minute budget (P12). A counterexample shrinks through up to six histories, and each one runs the real CLI.

Authority

P4 (register): a counterexample is filed as an issue with its replay line, and a rerun never hides it. Under the M phase-1 decision, a random counterexample that the base also fails is filed, not blocking. The determinism-as-main reading in PR #90 applies the same rule to determinism units. The greppable-stream law (maintainer request 2026-11-12) is the one that fails.

主要言語
JavaScript
スター
5
フォーク
1
平均マージ
8時間 31分
マージ済み PR(30日)
60

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

TanStack/oracles のほかの issue

TanStack/oracles の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。