Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Flaky: note_vector_flow_test 'forty notes' under parallel test load

Abierto
  • ¿Algo no está bien?
#282 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
30/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
dart
Área
testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Dart
Estrellas
2
Forks
2
Merge medio
18 h 23 min
PR fusionados (30 d)
40

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de basictech01/uniun

Todos los issues de basictech01/uniun

Issues similares

Más issues de Dart

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.