Search stuck and never finishes
还没有人认领这个 Issue。
- 主要语言
- Shell
- 星标
- 11.2k
- 派生
- 1.9k
- 平均合并
- 14 小时 16 分钟
- 30 天内合并 PR
- 6
描述
Describe the bug
I created a md to work around the issue, and it has the description
cat ~/.copilot/instructions/search-tool-workaround.instructions.md
Search / grep tool workaround
In this environment the built-in grep tool (and code-search tooling built on
it) can stall for minutes on the "Search" spinner, even though the underlying
ripgrep work completes in milliseconds. This is a tool-invocation-layer issue,
not a real search cost:
- Single-file ripgrep: ~2 ms
- Whole 70 GB / ~825k-file working tree: ~3.8 s
So the multi-minute "Search" hangs are NOT caused by ripgrep or repo size.
Guidance
- Prefer plain
grep/rgandview/cat/sedvia the bash tool for
searching file contents and reading files. These return in milliseconds. - Avoid the built-in
greptool here until the responsiveness bug is fixed. - Always scope searches to a specific path/file when possible
(e.g.grep -nE 'pattern' path/to/file).
Affected version
GitHub Copilot CLI 1.0.79
Steps to reproduce the behavior
everytime it needs to Search
Search "something" ....
which stuck forever
Expected behavior
No response
Additional context
No response
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先使用内置的 Search/grep 工具在 GitHub Copilot CLI 1.0.79 中复现挂起问题,然后将其与 ~/.copilot/instructions/search-tool-workaround.instructions.md 中描述的基于 bash 的 grep 或 rg 命令进行比较。跟踪 Search 的调用层,而不是 ripgrep 的性能。搜索能够完成,而不是一直停留在 Search spinner 上,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- shell
- 领域
- cli
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 活跃
- 描述清晰度
- 需要澄清
- 新手友好度
- 35/100