microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception Error refreshing Java upgrade issues cache for project: Bede.Wallet java.lang.AssertionError: popped operation[{name:'boundary/common.list_gradle_projects', method:listGradleRootProjectPojo}] is not the operation[{name:'Checki
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: 2025.3.4 IU-253.32098.37
OS: Mac OS X
JDK: JetBrains s.r.o. 21.0.10
Plugin version: 3.97.3-2025.3
Additional Info: None
Parent component:
com.intellij.openapi.wm.impl.IdeRootPane[,0,0,1400x826,invalid,layout=com.intellij.openapi.wm.impl.IdeRootPane$CustomHeaderRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]
Error message:
IdeaLoggingEvent[message=Error refreshing Java upgrade issues cache for project: Bede.Wallet, throwable=java.lang.AssertionError: popped operation[{name:'<REDACTED: user-file-path>', method:listGradleRootProjectPojo}] is not the operation[{name:'Checking Java upgrade issues'}] throwing exception
at com.microsoft.azure.toolkit.lib.common.operation.AzureOperationAspect.afterThrowing(AzureOperationAspect.java:84)
at com.microsoft.azure.toolkit.lib.common.operation.AzureOperationAspect.afterThrowing(AzureOperationAspect.java:43)
at com.microsoft.intellij.util.GradleUtils.listGradleRootProjectPojo(GradleUtils.java:38
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 by tracing the cache refresh through com.microsoft.intellij.util.GradleUtils.listGradleRootProjectPojo and com.microsoft.azure.toolkit.lib.common.operation.AzureOperationAspect.afterThrowing. Reproduce the Java upgrade issues refresh for the Bede.Wallet project in IntelliJ, then verify that the operation stack remains consistent and the assertion no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100