Open pwalessi-dell opened 3 months ago
I'm afraid any way to connect to IDE remotely will not work with the plugin due to JCEF limitaions :( We'll investigate the issue in details but for now we recommend to use plugin only with locally installed IDE
I am running the IDE locally in Windows pointed to my source code in WSL as explained here.
Hmm, @pwalessi-dell then what did you mean by "both host and client"? Do you use ide in local mode only? Or you use some kind of remote development setup?
I run my project like this: Open a project stored in the WSL file system In IntelliJ IDEA, you can directly open a project stored in the WSL file system and work with it like with any other project.
When I said, "I've disabled ide.browser.jcef.sandbox.enable on both the host and client" I was referring to the instruction in the Codium chat window that says, " 1. Navigate to the Help -> Find Action... and find(type) "Registry". Here disable ide.browser.jcef.sandbox.enable
option;"
When I Find Action for "Registry" there are 2 options: Registry... (On Host) and Registry... I set ide.browser.jcef.sandbox.enable on both.
I suspect that this configuration is running the back-end remotely in WSL and that's why the JCEF doesn't work. Do you know if a fix is planned for this, or, if it's possible to fix?
Unfortunately, seems no way for now to run plugin (not only jcef) in such host-client configuration. 😕 We'll try to explore that in the future but for now we support only ide running locally.
When I open the Codiumate chat window in the Windows client of IntelliJ while connected to a WSL project, I get a dialog that explains that, "Codiumate Plugin uses JCEF (Java Chromium Embedded Framework) to create a webview component in the plugin's tool window."
I've disabled ide.browser.jcef.sandbox.enable on both the host and client and I've ensured that I'm running boot runtime equipped with JCEF.
Any further help would be appreciated.