microsoft / microsoft/copilot-for-eclipse

[Bug] Error on conversation request: read ECONNRESET

Open
#332 7 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

Environment

  • OS: Windows
  • Eclipse Version: Eclipse 2026-06 (4.40)
  • Plugin Version: Copilot 0.19.0

Describe the bug
While using the GitHub Copilot Eclipse plugin, I saw the following in chat window:
Sorry, an error occurred while generating a response. Details: Error on conversation request: read ECONNRESET

In the Error Log, I saw the following entry:

eclipse.buildId=4.40.0.20260604-0652
java.version=21.0.11
java.vendor=Eclipse Adoptium
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=hu_HU
Framework arguments:  -product org.eclipse.epp.package.dsl.product -pluginCustomization plugin_customization.ini
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.dsl.product -pluginCustomization plugin_customization.ini

org.eclipse.lsp4e
Error
Wed Jul 01 07:18:17 CEST 2026
[LS:GitHub Copilot Language Server][Error]	[toolCallingLoop] Fetch failed: {
  type: 'failed',
  reason: 'Error on conversation request: read ECONNRESET',
  requestId: '0493baee-26bc-4e8d-9dcb-21ceea12487d',
  noRetry: undefined
}

Screenshots

Image Image

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 with the org.eclipse.lsp4e Error Log entry and the GitHub Copilot Language Server's toolCallingLoop failure for conversation requests on the stated Windows environment. Reproduce the ECONNRESET if possible, then identify and address the failure so chat requests complete reliably or the cause and handling are clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
desktop, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.