microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception com.intellij.openapi.vfs.InvalidVirtualFileAccessException: Accessing invalid virtual file: file://C:/Users/EBBHO/OneDrive - Bayer/Desktop/Automation/Farmrise/UI2/farmrise-UI-Automation/pom.xml; original:11; found:92109; File
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.5 IC-243.26053.27
OS: Windows 11
JDK: JetBrains s.r.o. 21.0.6
Plugin version: 3.94.0-2024.3
Additional Info: None
Parent component:
com.intellij.openapi.wm.impl.IdeRootPane[,7,7,1281x673,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> - <REDACTED: user-file-path>; original:11; found:92109; 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.MavenProjectReport
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 reading MavenProjectReportGenerator.checkDependencyManagement at MavenProjectReportGenerator.java:264 and the FileManagerImpl.findFile stack entry. Reproduce the IntelliJ 2024.3.5 Windows setup if possible, then determine when the reported invalid virtual file is accessed and verify that the uncaught exception no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100