Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Flaky: note_vector_flow_test 'forty notes' under parallel test load

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
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 小时
30 天内合并 PR
35

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

basictech01/uniun 的其他 Issue

查看 basictech01/uniun 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 发到你的邮箱

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