Repository navigation
Literal grep waits without progress before returning three matches #1321
Description
During review of commit f718fac76f4a32358da6d36dae66d546c6bf9a21 in a separate prod-code worktree, the command prod-code grep "proof verified clean" crates/prod-code-mcp stayed live with no stdout across repeated bounded observations while independent definition/outline calls completed. It eventually exited 0 and returned only three matches in tests/validate_diff_proposal.rs (lines 68, 170, 215). The overall delay exceeded one minute; an exact wall-clock benchmark was not captured and is not claimed. Expected: a bounded literal search returns promptly or reports which sync/search/enrichment phase is pending, without requiring the caller to guess whether it is stuck. Reproduce on a warm Linux node with this commit and the exact command. No service changes or repeat benchmark campaign were performed.
Environment
- client: prod-code 0.3.41 (commit 9a21810) on macos aarch64
- node: linux aarch64 (prod-code 0.3.41, commit 9a21810), engines: rust (ra_ap_ide), go (gopls), cpp (clangd), python (basedpyright-langserver), typescript (tsc --lsp), java (jdtls), kotlin (kotlin-language-server), generic-lsp
Filed with prod-code report-issue.
Activity
alex09x commentedon Oct 25, 2026
Another read-only occurrence on the current checkout:
prod-code grep 'MCP server|connection per call|re-opens|reconnect' ROADMAP.md --max-results 10The process was still alive at 52 seconds with no output. It eventually returned five matches successfully. This is a lower bound from process elapsed time, not a measured full duration. Nearby definition and outline queries completed quickly. No repository mutation or test was involved. A duplicate primary-started narrower query was stopped; only the original result was used.
alex09x commentedon Oct 28, 2026
PR #1712 also covers this single-file
ROADMAP.mdform: explicit files inside the checkout now use local ripgrep before the remote command path. The test exercises both no-match and matching results and confirms no remote exec. Workspace/directory-wide searches still use the remote-first path. The issue will close when the PR merges.