microsoft / microsoft/azure-tools-for-java

[IntelliJ] Uncaught Exception java.lang.NullPointerException: Cannot invoke "com.intellij.openapi.vfs.VirtualFile.getPath()" because the return value of "com.intellij.openapi.vfs.VirtualFile.getParent()" is null

Open
#11,918 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
262
Forks
185
Avg merge
2d 21h
Merged PRs (30d)
1

Description

IntelliJ build version: 2026.1 IU-261.22158.277
OS: Windows 11
JDK: JetBrains s.r.o. 25.0.2
Plugin version: 3.97.3-2026.1
Additional Info: None
Parent component:

com.intellij.openapi.wm.impl.IdeRootPane[,8,8,2560x1392,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=java.lang.NullPointerException: Cannot invoke "com.intellij.openapi.vfs.VirtualFile.getPath()" because the return value of "com.intellij.openapi.vfs.VirtualFile.getParent()" is null
	at com.microsoft.azure.toolkit.intellij.container.model.DockerImage.<init>(DockerImage.java:57)
	at com.microsoft.azure.toolkit.intellij.containerregistry.runner.ContainerRegistryDockerfileActionsProvider.getActions(ContainerRegistryDockerfileActionsProvider.java:17)
	at com.microsoft.azure.toolkit.intellij.containerregistry.runner.DockerRunLineMarkerProvider.lambda$getDockerfileActions$2(DockerRunLineMarkerProvider.java:105)
	at com.microsoft.azure.toolkit.intellij.containerregistry.runner.DockerRunLineMarkerProvider.getDockerfileActions(DockerRunLineMarkerProvider.java:108

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with DockerImage.java:57, then trace the callers in ContainerRegistryDockerfileActionsProvider.java and DockerRunLineMarkerProvider.java shown in the stack trace. Investigate the null VirtualFile parent case and check existing tests around Dockerfile actions; done means the reported IntelliJ action no longer throws this exception for a root-level file.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, java
Domain
cloud, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.