microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception com.intellij.openapi.vfs.InvalidVirtualFileAccessException: Accessing invalid virtual file: file://C:/WSVattenfall/projects/vpr_w11/vpr/bpp/pom.xml; original:463810; found:-; File.exists()=false
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.1.3 IU-251.26927.53
OS: Windows 11
JDK: JetBrains s.r.o. 21.0.7
Plugin version: 3.95.0-2025.1
Additional Info: None
Parent component:
com.intellij.openapi.wm.impl.IdeRootPane[,7,0,1386x769,layout=com.intellij.openapi.wm.impl.IdeRootPane$CustomHeaderRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]
Error message:
IdeaLoggingEvent[message=null, throwable=com.intellij.openapi.vfs.InvalidVirtualFileAccessException: Accessing invalid virtual file: <REDACTED: user-file-path>; original:463810; found:-; File.exists()=false
at com.intellij.psi.impl.file.impl.FileManagerImpl.findFile(FileManagerImpl.java:507)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.lambda$checkDependencyManagement$7(MavenProjectReportGenerator.java:269)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.checkDependencyManagement(MavenProjectReportGenerator.java:269)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.analyzePom(MavenProjectReportGenerator.java:158)
at com.microsoft.azure.to
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 inspecting MavenProjectReportGenerator, especially checkDependencyManagement at line 269 and analyzePom at line 158, using the reported FileManagerImpl.findFile stack frame as context. Reproduce the IntelliJ 2025.1.3 failure with the reported Maven project if possible, then verify that an invalid or missing virtual file no longer produces an uncaught exception.
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
- 25/100