[davidmichaelkarr]

My boss asked me to evaluate github copilot and the Eclipse plugin. I did what I had to do within my enterprise to get a license, and then I installed the copilot4eclipse plugin (in 2023-09). I then selected “Sign into Github Copilot…”, and it immediately renders an error dialog titled “Copilot Sign In Failure” with the message “Unable to sign in to Github Copilot at this time”. I’ve tried this several times.

I’m obviously behind a corporate firewall, and my Eclipse proxy settings are set so that I can get to outside locations, like the Eclipse Marketplace, which works fine.

[wayne]

Hi David,
Thx for sharing this info. The issue is most likely with the Copilot api which runs as a subprocess of Eclipse in nodejs. Can you try:

0) Note that when changes are made to the Eclipse proxy settings an Eclipse restart is required for Copilot4Eclipse to apply the changes. Typically a dialog will popup and notify of the need for an Eclipse restart.

1) Clear your Eclipse log and then run a login attempt. Look for any interesting entries in the Error log. If yes please share what you can. You can send any info you want kept private to info@genuitec.com which routes to the tech team.

2) You can get more info by running eclipsec.exe (or the similar executable for your platform) and a ton of info will spew to the console.

3) Try enabling LSP logging in your Eclipse preferences under the Window menu>Preferences>Language Servers>Log, look for the Copilot4Eclipse server and enable.

4) Can you share any info about your network security environment, e.g., kerberos, other…

Somewhere in these streams of info will hopefully be the root issue.

Lastly as Copilot4Eclipse is built on a similar tech stack as the Github Copilot plugins for other IDEs you may find this doc helpful for troubleshooting network issues: https://docs.github.com/en/copilot/troubleshooting-github-copilot/troubleshooting-network-errors-for-github-copilot

Let us know what you learn?

Regards,
Wayne
Copilot4Eclipse Team

[Author]

Posts