microsoft / microsoft/copilot-for-eclipse

[Bug] Error when using search tool in workspaces with 20 or more projects open

Open
#24 26 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
126
Forks
60
Avg merge
2d 6h
Merged PRs (30d)
5

Description

Environment

  • OS: Windows 11
  • Eclipse Version: 2026-03
  • Plugin Version: 0.16

Describe the bug
When Copilot is trying to search using the built in ripgrep tool in a larger-than-micro sized workspace (>= 20 projects, eg Maven or Gradle submodules) the tool fails with error messages related to task queue size exceeded:

[Error] [ripgrepProcessManager] Task queue limit reached: 20

To Reproduce
Steps to reproduce the behavior:

  1. Open a workspace with at least 20 projects open
  2. Assign a task to Copilot in Agent mode (task should require Copilot to search files)
  3. Search files task fails and Copilot failovers to using findstr in command line, requiring user approval continuously.

This pretty much forces you to constantly babysit Copilot and click Approve on the approval requests for using findstr

Expected behavior
Built in search tool should work even in workspaces with >= 20 projects

I understand the 20 queue limit is hard coded somewhere and it may be difficult to have it being adjustable. But it would be very much appreciated if at least the hard coded limit could be raised to something like 100 or 200.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the ripgrepProcessManager path used when an Agent-mode search runs in a workspace with at least 20 open projects, and reproduce the task queue limit error from the issue steps. Done means the built-in search completes in such a workspace without falling back to repeated findstr approval requests, with a regression check for the queue limit behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.