microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception java.lang.Throwable: com.microsoft.azure.toolkit.lib.common.messager.AzureMessager$Holder <clinit> requests com.microsoft.azure.toolkit.lib.common.messager.IAzureMessager instance. Class initialization must not depend on serv
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 262
- Forks
- 185
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
IntelliJ build version: 2024.2.1 Preview IU-242.21829.15
OS: Mac OS X
JDK: JetBrains s.r.o. 21.0.3
Plugin version: 3.91.0-2024.2
Additional Info: None
Parent component:
com.intellij.openapi.wm.impl.IdeRootPane[,0,0,1920x1080,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=java.lang.Throwable: com.microsoft.azure.toolkit.lib.common.messager.AzureMessager$Holder <clinit> requests com.microsoft.azure.toolkit.lib.common.messager.IAzureMessager instance. Class initialization must not depend on services. Consider using instance of the service on-demand instead.
at com.intellij.openapi.diagnostic.Logger.error(Logger.java:376)
at com.microsoft.azure.toolkit.intellij.common.messager.IntellijAzureMessager$Provider.getMessager(IntellijAzureMessager.java:172)
at com.microsoft.azure.toolkit.lib.common.messager.AzureMessager$Holder.loadMessager(AzureMessager.java:30)
at com.microsoft.azure.toolkit.lib.common.messager.AzureMessager$Holder.<clinit
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 IntellijAzureMessager.java at getMessager and AzureMessager.java at Holder.loadMessager, using the reported IntelliJ build and plugin versions to reproduce the exception. Done means class initialization no longer triggers the reported service-dependency error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100