microsoft / microsoft/azure-tools-for-java

[IntelliJ] Uncaught Exception java.lang.Throwable: Recursive conflict resolution for:PsiMethodCallExpression:map.from(this::getKeyDeserializer); file=PsiJavaFile:KafkaProperties.java

Open
#12,313 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.2.1 IU-262.9437.185
OS: Linux
JDK: JetBrains s.r.o. 25.0.3
Plugin version: 3.97.7-2026.2
Additional Info: None
Parent component:

com.intellij.openapi.wm.impl.IdeRootPane[,0,24,1920x1143,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.Throwable: Recursive conflict resolution for:PsiMethodCallExpression:map.from(this::getKeyDeserializer); file=PsiJavaFile:KafkaProperties.java
	at com.intellij.openapi.diagnostic.Logger.error(Logger.java:378)
	at com.microsoft.azure.toolkit.intellij.storage.code.java.ConnectionStringStorageClientAnnotator.annotate(ConnectionStringStorageClientAnnotator.java:56)

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 in ConnectionStringStorageClientAnnotator.annotate at line 56 and inspect the handling of the PsiMethodCallExpression in KafkaProperties.java. Reproduce with the listed IntelliJ, JDK, and plugin versions, then identify what triggers the recursive conflict-resolution exception and verify that the annotator no longer reports 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
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.