microsoft / microsoft/copilot-for-eclipse
Multiple unexpected warnings on Copilot startup
Nobody has claimed this yet.
- 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
Just start Eclipse with Copilot installed. There are always 3 warnings shown.
Logs (optional)
!ENTRY org.eclipse.lsp4e 2 0 2026-01-27 09:58:42.354
!MESSAGE [LS:GitHub Copilot Language Server][Warning] [McpAutoApproveService] Invalid McpAutoApproveService config, resetting to empty undefined
!ENTRY org.eclipse.lsp4e 2 0 2026-01-27 09:58:42.377
!MESSAGE [LS:GitHub Copilot Language Server][Warning] [default] Policy watcher not available - continuing without policy watching: Unsupported platform
!ENTRY org.eclipse.lsp4e 1 0 2026-01-27 09:58:42.377
!MESSAGE [LS:GitHub Copilot Language Server][Info] [GithubAvailableEmbeddingTypes] Could not find any available embedding types. Error: noSession
Expected behavior
- No warning is logged
- If a warning is shown, it has at least some stack attached
Actual behavior
- Warnings are reported during many Eclipse tests
- Warnings have no context, no idea how to "fix" them
The problem is that we have tests check for unexpected errors and warnings and now every time tests start (~30 times during our automated tests) we have multiple warnings reported as test failures. Our customers are also not accepting any warnings or errors in the logs "by default" in a freshly installed application.
This is a blocker for us for 0.15.0 use.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Eclipse startup with Copilot 0.15.0 and inspect the three logged messages from org.eclipse.lsp4e: McpAutoApproveService, policy watcher, and available embedding types. Check the automated tests that treat unexpected warnings as failures. Done means startup and repeated test runs no longer emit these uncontextualized warnings, or each remaining warning has useful context.
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
- Mostly clear
- Newbie friendliness
- 35/100