microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception provider: de.plushnikov.intellij.plugin.provider.LombokAugmentProvider@1caf87be com.intellij.openapi.diagnostic.RuntimeExceptionWithAttachments: Read access is allowed from inside read-action only (see Application.runReadActio
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.4 IU-242.23726.103
OS: Windows 11
JDK: JetBrains s.r.o. 21.0.4
Plugin version: 3.95.0-2024.2
Additional Info: None
Parent component:
com.intellij.openapi.wm.impl.IdeRootPane[,8,8,2048x1104,layout=com.intellij.openapi.wm.impl.IdeRootPane$MyRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]
Error message:
IdeaLoggingEvent[message=provider: de.plushnikov.intellij.plugin.provider.LombokAugmentProvider@1caf87be, throwable=com.intellij.openapi.diagnostic.RuntimeExceptionWithAttachments: Read access is allowed from inside read-action only (see Application.runReadAction()); see https:/<REDACTED: user-file-path> for details
Current thread: Thread[#217,pool-17-thread-1,5,main] 1102780984 (EventQueue.isDispatchThread()=false)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.analyzeCode(MavenProjectReportGenerator.java:206)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.inspectRootMavenProject(MavenProjectReportGenerator.j
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 MavenProjectReportGenerator.analyzeCode(MavenProjectReportGenerator.java:206), then inspect the surrounding inspectRootMavenProject flow. Reproduce the IntelliJ 2024.2.4 failure if possible and trace the reported read-access violation; done means the uncaught exception no longer occurs during the reported analysis.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100