microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception com.intellij.openapi.vfs.InvalidVirtualFileAccessException: Accessing invalid virtual file: file://C:/projects/intellij/dev/pmx-wbm-bff-ms/pom.xml; original:79504; found:122294; File.exists()=true
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.3.1.1 IU-243.22562.218
OS: Windows 10
JDK: JetBrains s.r.o. 21.0.5
Plugin version: 3.94.0-2024.3
Additional Info: None
Parent component:
com.intellij.openapi.wm.impl.IdeRootPane[,6,6,1537x921,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:79504; found:122294; File.exists()=true
at com.intellij.psi.impl.file.impl.FileManagerImpl.findFile(FileManagerImpl.java:378)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.lambda$checkDependencyManagement$7(MavenProjectReportGenerator.java:264)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.checkDependencyManagement(MavenProjectReportGenerator.java:264)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.analyzePom(MavenProjectReportGenerator.java:158)
at com.microsoft.azur
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 MavenProjectReportGenerator.checkDependencyManagement at line 264 and the FileManagerImpl.findFile stack frame. Review the reported IntelliJ 2024.3.1.1, Windows 10, JDK 21.0.5, and plugin 3.94.0 versions, then investigate a reproducible Maven-project case. Done means the reported InvalidVirtualFileAccessException no longer occurs during POM analysis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100