microsoft / microsoft/copilot-for-eclipse
"unhandledRejection" error
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.16.0.202604201810_nightly
Eclipse IDE and version
4.40 latest nightly I20260421-1800
Platform
Just some code browsing in java code, switching from one editor to other, noticed this error reported int he error log.
null
org.eclipse.lsp4e
Error
Wed Apr 22 15:12:23 CEST 2026
[LS:GitHub Copilot Language Server][Error] [default] unhandledRejection: Error: Tests: either GITHUB_PAT, GITHUB_OAUTH_TOKEN, or GITHUB_OAUTH_TOKEN+VSCODE_COPILOT_CHAT_TOKEN must be set unless running from an IS_SCENARIO_AUTOMATION environment. Run "npm run get_token" to get credentials.
at Flt.tokenProvider (/snapshot/copilot-intellij/dist/main.js:1440:8372)
at Object.get accessToken [as accessToken] (/snapshot/copilot-intellij/dist/main.js:1311:3830)
at Flt._handleAuthChangeEvent (/snapshot/copilot-intellij/dist/main.js:780:10408)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
Steps to reproduce
No steps
Logs (optional)
No response
Expected behavior
No errors
Actual behavior
Error logged sometimes
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 with the authentication flow around tokenProvider, accessToken, and _handleAuthChangeEvent shown in the error, noting that the report comes through org.eclipse.lsp4e during Eclipse code browsing. Reproduce the intermittent error if possible and compare it with the npm run get_token credential requirement. Done means the same situation no longer produces an unexpected error log.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100