microsoft / microsoft/copilot-for-eclipse

CLS may be started two times in parallel

Open
#87 2 comments 0 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

Feedback source

None

GitHub Copilot plugin version

0.15.0

Eclipse IDE and version

4.38

Platform

RHEL 9.6

Steps to reproduce

No steps, found in our automated test logs.
We randomly see that CLS startup might be triggered two times, there are probably at least two different places where it could init itself and these are not synchronized? The second one is surely from earlyStartup, but if the CLS can start by loading some other extension point, earlyStartup extension point might make no sense anymore?

Logs (optional)

The log looks like this:

!ENTRY com.microsoft.copilot.eclipse 1 0 2026-02-03 00:17:45.973
!MESSAGE [Info] Starting language server with binary lsp agent.

!ENTRY com.microsoft.copilot.eclipse 1 0 2026-02-03 00:17:45.976
!MESSAGE [Info] Found native binary in fragment bundle: com.microsoft.copilot.eclipse.core.agent.linux.x64

!ENTRY com.microsoft.copilot.eclipse 1 0 2026-02-03 00:17:46.734
!MESSAGE [Info] Binary agent started successfully.

!ENTRY com.microsoft.copilot.eclipse 1 0 2026-02-03 00:17:47.230
!MESSAGE [Info] Starting language server with binary lsp agent.

!ENTRY com.microsoft.copilot.eclipse 1 0 2026-02-03 00:17:47.230
!MESSAGE [Info] Found native binary in fragment bundle: com.microsoft.copilot.eclipse.core.agent.linux.x64

!ENTRY com.microsoft.copilot.eclipse 1 0 2026-02-03 00:17:47.283
!MESSAGE [Info] Binary agent started successfully.

!ENTRY org.eclipse.lsp4e 2 0 2026-02-03 00:17:52.240
!MESSAGE The server did not stop after 5 seconds
Expected behavior

No extra warnings on startup, only one CLS native startup.

Actual behavior

CLS starts two times, warning The server did not stop after 5 seconds is reported.

Additional information

No response

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 startup paths mentioned in the report, especially the earlyStartup extension point and any other extension point that can initialize CLS. Use the automated test logs and the duplicated startup messages as the reproduction signal. Done means startup triggers only one CLS native launch and no server-stop warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.