Description
When running from the home directory, calling Glob "**/dbt_project.yml" hangs indefinitely (1+ hours with no response). The recursive glob pattern scans the entire filesystem tree from the home directory without any timeout or scope limit.
Reported by user FrankTub in #623 (external report).
Root Cause
Ripgrep.files() is spawned with --files --hidden from a broad directory with no timeout. The --hidden flag makes it worse (scans .cache, .npm, .local, etc.). Home directory isn't a git repo, so no .gitignore helps.
Fix
- Add a 30-second timeout using
abortAfter utility
- Return partial results on timeout with a helpful message guiding users to narrow their search
- Kill the
rg child process immediately on early exit (100-file limit or timeout) via localAbort controller
- Properly distinguish timeout errors from real errors (ENOENT, permissions) — only swallow
AbortError from timeout signal
Upstream Context
Upstream has related issues (#18954 infinite loops, #5220 100% CPU) but no merged fixes yet.
Description
When running from the home directory, calling
Glob "**/dbt_project.yml"hangs indefinitely (1+ hours with no response). The recursive glob pattern scans the entire filesystem tree from the home directory without any timeout or scope limit.Reported by user
FrankTubin #623 (external report).Root Cause
Ripgrep.files()is spawned with--files --hiddenfrom a broad directory with no timeout. The--hiddenflag makes it worse (scans.cache,.npm,.local, etc.). Home directory isn't a git repo, so no.gitignorehelps.Fix
abortAfterutilityrgchild process immediately on early exit (100-file limit or timeout) vialocalAbortcontrollerAbortErrorfrom timeout signalUpstream Context
Upstream has related issues (#18954 infinite loops, #5220 100% CPU) but no merged fixes yet.