-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception when used in remote development #140
Comments
Is that all the exception? And, are there other exceptions preceding that one? |
Yes, that's all. When I startup the wsl project, I get a red ! in the bottom right corner and when I click on it, i get the "IDE Internal Errors" Dialog where this Exception is shown. The plugin seems to work after the exception though. |
Well I just got this Exception during commit (not sure if they are related):
|
It looks like the remote environment has more limitations, that is, some parts of the platform are not loaded. I'd have to experiment myself. Or check with JetBrains. |
Could you post the exact IDEA version you're running on? |
The version is: Thanks so far. If I remember correctly the plugin wasn't working at all in 2023.x and even the commit panel wasn't accessible. Now just the errors are popping up. |
Yup I had already solved some issues related to Gateway / remote development. Maybe that's yet again something that has changed and that I need to align on my side (e.g., loading parts of the plugin only if the platform dependency is present). |
To add onto this issue, for some reason, when the plugin is enabled during JetBrains Gateway, I am simply unable to type parentheses in editor windows (both Git message editor window and Code editor window). Disabling the plugin fixes the issue. |
That's pretty strange. I guess the only way for me to repro would be to set up Gateway. Never tried doing that. |
Here are the log errors:
and a bit later, also during the startup:
|
Another update. All the issues seem to be resolved, if you enable the plugin on the Host side, but disable it on the Client side. For context, due to settings synchronization in IntelliJ, the plugin gets installed on both client and host (if you use Gateway), and is automatically enabled on both sides. This seems to cause issues, because if you disable the plugin on the client, but keep it enabled on the host machine (the one you connect to), everything seems to work properly: no issues with typing parenthesis, while the configuration is still properly read and autocompletion works. Hope this helps. |
This is what I don't get.
I don't understand why that platform class isn't found. |
Maybe I need to use reflection and catch the |
The following Exception occurs every time I open a project in a Windows IDEA connected to WSL.
java.lang.IllegalArgumentException: Missing extension point: com.github.lppedd.idea-conventional-commit.commitInspectionProvider in container Application (IR on EDT disabled) at com.intellij.openapi.extensions.impl.ExtensionsAreaImpl.getExtensionPoint(ExtensionsAreaImpl.kt:273) at com.intellij.openapi.extensions.BaseExtensionPointName.getPointImpl(BaseExtensionPointName.kt:19) at com.intellij.openapi.extensions.ExtensionPointName.getExtensionList(ExtensionPointName.kt:54) at com.github.lppedd.cc.api.impl.InternalCommitInspectionProviderService.getInspectionProviders(InternalCommitInspectionProviderService.kt:17) at com.github.lppedd.cc.inspection.CommitInspectionsRegistrarStartupActivity.runActivity(CommitInspectionsRegistrarStartupActivity.kt:19) at com.intellij.ide.startup.impl.StartupManagerImpl.runOldActivity(StartupManagerImpl.kt:319) at com.intellij.ide.startup.impl.StartupManagerImpl.access$runOldActivity(StartupManagerImpl.kt:68) at com.intellij.ide.startup.impl.StartupManagerImpl$runPostStartupActivities$5$1.invoke(StartupManagerImpl.kt:270) at com.intellij.ide.startup.impl.StartupManagerImpl$runPostStartupActivities$5$1.invoke(StartupManagerImpl.kt:269) at com.intellij.openapi.progress.CoroutinesKt.blockingContextInner(coroutines.kt:320) at com.intellij.openapi.progress.CoroutinesKt.access$blockingContextInner(coroutines.kt:1) at com.intellij.openapi.progress.CoroutinesKt$blockingContext$2.invokeSuspend(coroutines.kt:197) at com.intellij.openapi.progress.CoroutinesKt$blockingContext$2.invoke(coroutines.kt) at com.intellij.openapi.progress.CoroutinesKt$blockingContext$2.invoke(coroutines.kt) at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:78) at kotlinx.coroutines.CoroutineScopeKt.coroutineScope(CoroutineScope.kt:264) at com.intellij.openapi.progress.CoroutinesKt.blockingContext(coroutines.kt:196) at com.intellij.ide.startup.impl.StartupManagerImpl.runPostStartupActivities(StartupManagerImpl.kt:269) at com.intellij.ide.startup.impl.StartupManagerImpl.access$runPostStartupActivities(StartupManagerImpl.kt:68) at com.intellij.ide.startup.impl.StartupManagerImpl$runPostStartupActivities$3$2.invokeSuspend(StartupManagerImpl.kt:191) at com.intellij.ide.startup.impl.StartupManagerImpl$runPostStartupActivities$3$2.invoke(StartupManagerImpl.kt) at com.intellij.ide.startup.impl.StartupManagerImpl$runPostStartupActivities$3$2.invoke(StartupManagerImpl.kt) at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:78) at kotlinx.coroutines.BuildersKt__Builders_commonKt.withContext(Builders.common.kt:167) at kotlinx.coroutines.BuildersKt.withContext(Unknown Source) at com.intellij.ide.startup.impl.StartupManagerImpl$runPostStartupActivities$3.invokeSuspend(StartupManagerImpl.kt:190) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:793) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:697) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:684)
The text was updated successfully, but these errors were encountered: