[Marlonlord]

every time i try to connect to GitHub i get this error(Title) i am using the Steam Deck which has a modified version of Arch Linux i also had much trouble to install the node.js but fixed this at the end. I already tried to reinstall the plugin and Eclipse itself but nothing worked the only thing i noticed is that if i reinstall the plugin and restart eclipse the first time i actually don’t get the error and it shows me the code to login but i cant open the website if i manually type the url and enter the Code it says it is connected but the plugin still says i am not logged in if i then restart eclipse the error occurs again. For me It looks like something is blocking the connection i also tried disabling the Firewall but it still dosent work. I also want to say that i have this plugin installed on my Windows Laptop and it works perfectly fine maybe that has something to do with the error

[wayne]

Hi,
Thanks for the info, especially the that Copilot4Eclipse on a Windows system is working for you.

1) Are there any interesting entries in the Eclipse error log?

2) Are you behind a corporate firewall?
If yes, is your Eclipse version configured to access the internet?
If yes and yes 🙂 does your corporate proxy perform SSL inspection/snooping?

3) This is just speculation based on proper operations on your Windows system: We have seen an issue on older Linux systems where the Copilot4Eclipse api which runs as a nodejs v18 subprocess is not compatible with a specific linux system. The workaround is to have Copilot4Eclipse use your local version of Node v16 or greater. You can quickly test this by using something like nvm to install Node v18 and see if it runs on your system. If Node v18 does not run repeat the process to install and test Node v16. If either Node version works ping me and we will provide workaround instructions. Actually I’m doc’ing this up for inclusion in the Copilot4Eclipse online documentation.

Regards,
Wayne
Copilot4Eclipse Team

[Marlonlord]

Hello there i figured out what the problem was i simply had the wrong version of Eclipse i downloaded it from the discovery store that is installed on the Steam Deck i now downloaded Eclipse from the official website and the Copilot is now working perfect. Thanks for the help and quick response.

[aldhor333]

Good afternoon:

I just upgraded to version 1.2.0.202405271006-EA2 and I am getting error with the latest Spring Tool Suite version 44.22.1.RELEASE for macOS.

Eclipse Platform
Version: 4.31.0.v20240229-1022
Build id: I20240229-0520

Eclipse Java Development Tools
Version: 3.19.400.v20240229-0520
Build id: I20240229-0520

Eclipse User Storage
Version: 1.2.0.v20210517-0327 (build 1733)

Eclipse RCP
Version: 4.31.0.v20240229-0520

`
java.util.concurrent.CompletionException: java.lang.RuntimeException: Exception occurred while creating an instance of the stream connection provider
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1770)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1760)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:507)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1491)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:2073)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:2035)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:187)
Caused by: java.lang.RuntimeException: Exception occurred while creating an instance of the stream connection provider
at org.eclipse.lsp4e.LanguageServersRegistry$ExtensionLanguageServerDefinition.createConnectionProvider(LanguageServersRegistry.java:170)
at org.eclipse.lsp4e.LanguageServerWrapper.lambda$0(LanguageServerWrapper.java:291)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
… 6 more
Caused by: org.eclipse.core.runtime.CoreException: Plug-in “com.genuitec.copilot4eclipse.chat” was unable to instantiate class “com.genuitec.copilot4eclipse.lsp.CopilotProcessStreamConnectionProvider”.
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:242)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:235)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:987)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:255)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:65)
at org.eclipse.lsp4e.LanguageServersRegistry$ExtensionLanguageServerDefinition.createConnectionProvider(LanguageServersRegistry.java:167)
… 8 more
Caused by: java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:74)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:486)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:233)
… 12 more
Caused by: java.lang.NoSuchMethodError: ‘byte[] org.apache.commons.io.IOUtils.byteArray()’
at org.apache.commons.compress.utils.IOUtils.skip(IOUtils.java:282)
at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.getNextTarEntry(TarArchiveInputStream.java:409)
at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.getNextEntry(TarArchiveInputStream.java:389)
at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.getNextEntry(TarArchiveInputStream.java:49)
at org.eclipse.wildwebdeveloper.embedder.node.CompressUtils.extractArchive(CompressUtils.java:71)
at org.eclipse.wildwebdeveloper.embedder.node.CompressUtils.unarchive(CompressUtils.java:52)
at org.eclipse.wildwebdeveloper.embedder.node.NodeJSManager.getNodeJsLocation(NodeJSManager.java:85)
at com.genuitec.copilot4eclipse.lsp.CopilotProcessStreamConnectionProvider.init(Unknown Source)
at com.genuitec.copilot4eclipse.lsp.CopilotProcessStreamConnectionProvider.<init>(Unknown Source)
at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
… 15 more
`

Thank you in advance!
Jorge

[wayne]

@aldhor333

Thanks for sharing the stacktrace.

The stacktrace indicates that Copilot4Eclipse’s client api process (a nodejs process) is not being started. This due to our embedded nodejs plugin is goofing up extracting a nodejs engine.

0) What version of macos are you running?

1) Do you have any type of antivirus software that might be trapping the nodejs extraction process?

2) If you restart Eclipse does the problem disappear or is it still present?

I will try to replicate your experience tonight.

Wayne
Copilot4Eclipse Team

[aldhor333]

Hi Wayne:
Thank you very much for your quick response and kindness.

0) Apple M2 Pro – Sonoma 14.5
1) I do not have administrator permissions. It is a company computer for which I have limited installation permissions.
2) I restart Eclipse and the problem persist :/ I try restarting the computer and the problem persist.

I guess the nodejs engine is something new in EA2 (Persistable Chat Conversations maybe?), since EA1 did not have that problem.

Thanks again for your time
Jorge

[wayne]

Thx.

I installed STS 4.22 on macos/M1/sonoma 14.1 followed by Copilot4Eclipse 1.2EA2. No issues observed with Copilot4Eclipse operation on STS.

I then noticed that “Check for Updates” identifies Wild Web Dev editors v1.36.x & WWD XML v1.34.x. Have you installed either of these updates? If not, please do not install them. If yes, can your roll them back including the node.embedder plugin. Preliminary: I noticed something goofy with the WWD update, e.g., it looks like the WWD update introduces a Java 21 dependency. I will investigate and follow up tomorrow.

W

[aldhor333]

Indeed, I updated WWD 1.3.6

Thank you very much Wayne!

[aldhor333]

Uninstalling both WWD and Copilot4Eclipse (to download again your version of Node.js, otherwise it was still with the version provided with WWD) works perfectly.

I leave you the versions used by each component in case it helps you.

Thanks for solving my problem so fast!

Wild Web Developer HTML, CSS, JSON, Yaml, JavaScript, TypeScript, Node tools 1.3.6.202405280856
|— Node.js embedder from Wild Web Developer 1.1.2.202405271237

Copilot4Eclipse 1.2.0.202405271006-EA2
|— Node.js embedder from Wild Web Developer 1.0.7.202310251358

[wayne]

After doing some research this morning I found that the WWD 1.3.6 update introduces a Java 21 requirement on WWD and any dependent plugins that use the associated Node.js embedder 1.1.2 plugin. Thus the WWD 1.3.6 update breaks WWD in Eclipse 2024-3 running Java 17 and earlier Eclipse version. Consequentually, Copilot4Eclispe is also broken by the update.

Eclipse 4.32 (2024-6) is scheduled to release June 12 and it will include Java 21. Unfortunately, Eclipse will let you install this WWD update in Eclipse running Java 17 and break WWD, Copilot4Eclipse and other tools that run nodejs language servers, e.g., tabnine, codeium, …

What to do:
1) Avoid installing WWD 1.3.6 in your Eclipse/Java 17 environments.
or
2) Upgrade to the Eclipse 4.32 (2024-6) when it is released on June 12. You/your org will need to be Java 21 ready.
or
3) Upgrade to JDK 21 and try running your Eclipse app with it in place of Java 17.
or
4) If you already installed WWD 1.3.6 in your Eclipse/Java17 environment and found WWD and Copilot4Eclipse are broken, consider rolling back to the previous WWD/Node-embed versions as they are compatible with Java 17.

Wayne

• This reply was modified 7 months, 2 weeks ago by wayne.

[Author]

Posts