Ripgrep Process Timeout Error When Analyzing Projects

[RLWJR]

Ripgrep Process Timeout Error When Analyzing Projects

Environment

• Traycer Version: 2.11.0
• IDE: Windsurf (VSCode-based)
• OS: Windows 10 (Build 19045.6332)
• Platform: win32-x64

Issue Description

Traycer fails to generate plans for any task due to a ripgrep process timeout error. This occurs even on small projects (442 files, 2MB total size).

Error Message

Failed to generate plan for task "Take a look at the project in x:bballcrew" due to "Error: ripgrep process timed out"

Steps to Reproduce

1. Open a project directory in Windsurf/VSCode with Traycer installed
2. Create a new Traycer task with any description (e.g., "Take a look at the project")
3. Traycer attempts to scan the workspace with ripgrep
4. Error occurs: ripgrep process timed out

Actual Behavior

Traycer cannot complete the initial workspace scan and fails during plan generation.

From Traycer.log (2025-10-04 16:26:25):

2025-10-04 16:32:16.955 [warning] Error getting folders for workspace {"error":"ripgrep process timed out"}
2025-10-04 16:33:00.533 [warning] Failed to generate plan for task ripgrep process timed out
2025-10-04 16:33:00.673 [error] PlanGenerationFailedError: Error: ripgrep process timed out
	at w1.generatePlan (c:\Users\Rick\.windsurf\extensions\traycer.traycer-vscode-2.11.0-win32-x64\out\extension.js:7:379608)

Expected Behavior

Traycer should successfully scan the workspace and generate a plan, or provide configurable timeout settings for larger projects.

Project Details

• Total Files: 442 files
• Total Size: 2.0 MB
• Git Repository: Yes (.git directory ~1.3MB)
• Structure: Standard Python project with typical directories (pycache, .git, .github, docs, data, etc.)

Workarounds Attempted

None successful. The timeout appears to be hardcoded in the extension.

Suggested Solutions

1. Increase default ripgrep timeout - Current timeout is too aggressive even for small projects
2. Add configuration setting - traycer.ripgrepTimeout setting to allow users to adjust based on project size
3. Respect .gitignore/.rgignore - Ensure ripgrep properly excludes directories like .git during workspace scanning
4. Progressive timeout - Start with shorter timeout, retry with longer timeout if needed

Additional Context

The project structure is clean and follows standard Python conventions. The .git directory (1.3MB) may be contributing to the timeout, but excluding it would prevent Traycer from understanding the full codebase context.

Impact

This issue makes Traycer completely unusable for affected projects, regardless of their size.

Contact

Available for additional debugging information if needed.

[hdkshingala]

Thank you, @RLWJR, for bringing this to our notice and writing a detailed description of the issue and the expected behaviour.

We will investigate this issue and develop a solution as soon as possible.