microsoft / microsoft/azure-tools-for-java

[IntelliJ][ReportedByUser] Uncaught Exception com.intellij.diagnostic.PluginException: Cannot create extension (class=com.microsoft.azure.toolkit.intellij.connector.code.function.FunctionAnnotationTypeHandler) [Plugin: com.microsoft.tooling.msservices.intellij.azure]

Open
#8,333 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: 2024.1 IU-241.14494.240
OS: Linux
JDK: JetBrains s.r.o. 17.0.10
Plugin version: 3.87.0-2024.1
Additional Info: None
Parent component:

com.intellij.openapi.wm.impl.IdeRootPane[,0,0,3782x2160,invalid,layout=com.intellij.openapi.wm.impl.IdeRootPane$MyRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]

Error message:

IdeaLoggingEvent[message=null, throwable=com.intellij.diagnostic.PluginException: Cannot create extension (class=com.microsoft.azure.toolkit.intellij.connector.code.function.FunctionAnnotationTypeHandler) [Plugin: com.microsoft.tooling.msservices.intellij.azure]
	at com.intellij.serviceContainer.ComponentManagerImpl.createError(ComponentManagerImpl.kt:988)
Caused by: java.io.UncheckedIOException: java.io.IOException: <REDACTED: user-file-path>
Caused by: java.io.IOException: <REDACTED: user-file-path>
Caused by: java.io.EOFException: Expected central directory size 91370 but only at 1617156 no valid central directory file header signature

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 the FunctionAnnotationTypeHandler extension named in the error and the IntelliJ plugin extension registration. Reproduce on IntelliJ 2024.1 with plugin version 3.87.0 and inspect the reported EOF and invalid central-directory errors. Done means the extension no longer causes an uncaught PluginException under the reported environment, with regression coverage if an existing test location is identified.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.