Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Flaky: note_vector_flow_test 'forty notes' under parallel test load

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

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

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

評価

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

調査の方向性

Start with test/integration/note_vector_flow_test.dart, the test named "forty notes are each found first by their own text", and the drained() helper and fake embedder it uses. Reproduce by running the file repeatedly under --concurrency=4 and record the found count on any failure, which separates a drain race from ANN recall misses. Done means the flake is explained with evidence and either the assertion or the drain wait is changed so repeated parallel runs pass.

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

説明

P3-Low

Summary

test/integration/note_vector_flow_test.dart › "forty notes are each found first by their own text" failed once during a full-suite run at --concurrency=4 (all other runs pass). Root cause not confirmed; filing so it is tracked rather than rediscovered.

What I verified

  • Passes in isolation and 3 of 3 repeated runs of the file at --concurrency=4, and in 3 full-suite runs of #88 work.
  • The failure was observed once, while the full suite was running 4 test files in parallel. I did not capture the assertion output (found count) at the time.

Likely causes (hypotheses, not proven)

  1. Timing under CPU contention: the test publishes 40 notes then waits on drained(); the fake embedder awaits a 2 ms Future.delayed per note and the test has a 2-minute timeout. Under 4-way parallel isolates plus tostore's own isolate, drained() may return before the last vector is flushed, or ask() can run while the index is still being built.
  2. tostore index state: AGENTS/CLAUDE notes that tostore 3.5 ANN search returns 99-100% recall (not 100%) on stored vectors; with 40 near-identical "alpha beta" tails an ANN miss would give found == 39. A genuine 99% recall figure makes this assertion (found == 40) inherently probabilistic.

Suggested next steps

  • Re-run the file in a loop (50x) under --concurrency=4 and record found on failure to tell (1) from (2).
  • If it is ANN recall, relax the assertion to a threshold (for example ≥ 38 of 40) or make the test deterministic by querying with the exact stored vector.
  • If it is a drain race, have drained() also wait for the store's flush.

Not a product bug as far as I can tell; it is CI flakiness risk. Refs #88

主要言語
Dart
スター
2
フォーク
2
平均マージ
1日 7時間
マージ済み PR(30日)
35

環境構築

はじめの一歩

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

basictech01/uniun のほかの issue

basictech01/uniun の issue をすべて見る

似ている issue

Dart の issue をもっと見る

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

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