microsoft / microsoft/azure-tools-for-java
[IntelliJ][ReportedByUser] Uncaught Exception com.intellij.diagnostic.PluginException: Cannot init component state (componentName=connections, componentClass=Impl) [Plugin: com.microsoft.tooling.msservices.intellij.azure]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 262
- Forks
- 185
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
IntelliJ build version: 2022.2.3 IC-222.4345.14
OS: Windows 10
JDK: JetBrains s.r.o. 17.0.4.1
Plugin version: 3.69.0-2022.2
Additional Info: None
Parent component:
com.intellij.openapi.wm.impl.IdeRootPane[,7,0,1502x1281,layout=com.intellij.openapi.wm.impl.IdeRootPane$MyRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]
Error message:
IdeaLoggingEvent[message=null, throwable=com.intellij.diagnostic.PluginException: Cannot init component state (componentName=connections, componentClass=Impl) [Plugin: com.microsoft.tooling.msservices.intellij.azure]
at com.intellij.configurationStore.ComponentStoreImpl.initComponent(ComponentStoreImpl.kt:148)
at com.microsoft.azure.toolkit.intellij.connector.ResourceConnectionExplorer$ToolWindowFactory.shouldBeAvailable(ResourceConnectionExplorer.java:112)
Caused by: java.lang.IllegalStateException: C:\Users\sungc\AppData\Roaming\JetBrains\IdeaIC2022.2\plugins\Kotlin\kotlinc doesn't exist
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 stack trace at com.microsoft.azure.toolkit.intellij.connector.ResourceConnectionExplorer.shouldBeAvailable, especially ResourceConnectionExplorer.java line 112, and inspect how the connections component is initialized. Reproduce with IntelliJ IDEA 2022.2.3, plugin 3.69.0-2022.2, and the reported Windows environment; done should mean the plugin no longer throws this initialization exception when the reported Kotlin path is absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100