microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception java.lang.Throwable: com.microsoft.azure.toolkit.lib.common.task.AzureTaskManager$Holder <clinit> requests com.microsoft.azure.toolkit.lib.common.task.AzureTaskManager instance. Class initialization must not depend on service
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.0.2 IU-242.20224.419
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,1512x895,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.task.AzureTaskManager$Holder <clinit> requests com.microsoft.azure.toolkit.lib.common.task.AzureTaskManager 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.task.IntellijAzureTaskManager$Provider.getTaskManager(IntellijAzureTaskManager.java:144)
at com.microsoft.azure.toolkit.lib.common.task.AzureTaskManager$Holder.loadTaskManager(AzureTaskManager.java:39)
at com.microsoft.azure.toolkit.lib.common.task.AzureTaskManager$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 AzureTaskManager.java around Holder.loadTaskManager and IntellijAzureTaskManager.java around Provider.getTaskManager, using the provided stack trace and IntelliJ/JDK/plugin versions to reproduce the error. Trace the class-initialization path and verify the completed change no longer logs the service-dependency exception during IntelliJ startup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100