Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] There a a lot of didChange notification with empty payload

Open
#397 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start by tracing the Java handling of the copilot/hook/didChange, copilot/customAgent/didChange, copilot/customPrompt/didChange, and copilot/customInstruction/didChange notifications. Reproduce initialization and verify that these notifications are not emitted with empty params or before initialize.

Written by the indexing model from the issue text.

Description

bug

Some of them even come before initialize

{"jsonrpc":"2.0","method":"copilot/hook/didChange","params":{}}
{"jsonrpc":"2.0","method":"copilot/customAgent/didChange","params":{}}
{"jsonrpc":"2.0","method":"copilot/customPrompt/didChange","params":{}}
{"jsonrpc":"2.0","method":"copilot/customInstruction/didChange","params":{}}

Dominant language
Java
Stars
125
Forks
63
Avg merge
1d 4h
Merged PRs (30d)
4

Getting set up

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.

More from microsoft/copilot-for-eclipse

All issues in microsoft/copilot-for-eclipse

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.