René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[FR] Communicate when a zoekt search limit is hit","articleBody":"## Problem\n\nWe have a set of configurable limits that Zoekt uses to determine when to terminate a search:\n\n```\nSHARD_MAX_MATCH_COUNT // Maximum number of matches: skip all processing an index shard after we found this many non-overlapping matches.\nTOTAL_MAX_MATCH_COUNT //  Maximum number of matches: stop looking for more matches once we have this many matches across shards.\nZOEKT_MAX_WALL_TIME_MS // Abort the search after this much time has passed.\n```\n\nCurrently, 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.,\n- \"does X exist anywhere?\" (this could hit the max wall time)\n- \"how many instances of Y exist?\" (this could hit both the max wall time and the max match counts)\n\n## Proposed Solution\n\nAdd some UX to communicate when a search limit has been hit and why.\n\nRelated #495 ","author":{"url":"https://github.com/brendan-kellam","@type":"Person","name":"brendan-kellam"},"datePublished":"2025-09-11T23:55:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/504/sourcebot/issues/504"}