Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Flaky: note_vector_flow_test 'forty notes' under parallel test load

Aperta
  • Qualcosa non va?
#282 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
dart
Ambito
testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Dart
Stelle
2
Fork
2
Merge medio
1g 7h
PR unite (30g)
35

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di basictech01/uniun

Tutte le issue di basictech01/uniun

Issue simili

Altre issue su Dart

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.