Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[FR] Communicate when a zoekt search limit is hit

未關閉
#504 1 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
48/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
冷清
領域
search

研究方向

Start by tracing where SHARD_MAX_MATCH_COUNT, TOTAL_MAX_MATCH_COUNT, and ZOEKT_MAX_WALL_TIME_MS are enforced, then review related issue #495. Define the user-facing and log signals for each limit, including which limit caused termination, and verify that exhaustive queries clearly indicate incomplete results.

由索引模型根據 Issue 內容生成。

描述

Feature

Problem

We have a set of configurable limits that Zoekt uses to determine when to terminate a search:

SHARD_MAX_MATCH_COUNT // Maximum number of matches: skip all processing an index shard after we found this many non-overlapping matches.
TOTAL_MAX_MATCH_COUNT //  Maximum number of matches: stop looking for more matches once we have this many matches across shards.
ZOEKT_MAX_WALL_TIME_MS // Abort the search after this much time has passed.

Currently, there is no UX or logs to signal when these limits are hit, resulting in inaccurate results and user confusion. This is especially bad for queries that need to be exhaustive, e.g.,

  • "does X exist anywhere?" (this could hit the max wall time)
  • "how many instances of Y exist?" (this could hit both the max wall time and the max match counts)

Proposed Solution

Add some UX to communicate when a search limit has been hit and why.

Related #495

主要語言
TypeScript
星號
3.9k
分支
374
平均合併
22 小時 33 分鐘
30 天內合併 PR
39

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

sourcebot-dev/sourcebot 的其他 Issue

查看 sourcebot-dev/sourcebot 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。