microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception Error retrieving vulnerability data from GitHub Security Advisory API java.io.IOException: Connection reset
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: 2026.2.1 IU-262.9437.185
OS: Windows 11
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[,8,8,1920x1032,layout=com.intellij.openapi.wm.impl.IdeRootPane$CustomHeaderRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]
Error message:
IdeaLoggingEvent[message=Error retrieving vulnerability data from GitHub Security Advisory API, throwable=java.io.IOException: Connection reset
at <REDACTED: user-file-path>(HttpClientImpl.java:938)
at com.microsoft.azure.toolkit.intellij.appmod.javaupgrade.service.CVECheckService.retrieveVulnerabilityData(CVECheckService.java:312)
at com.microsoft.azure.toolkit.intellij.appmod.javaupgrade.service.CVECheckService.fetchCves(CVECheckService.java:241)
at com.microsoft.azure.toolkit.intellij.appmod.javaupgrade.service.CVECheckService.getCveUpgradeIssues(CVECheckService.java:200)
at com.microsoft.azure.toolkit.intellij.appmod.javaupgrade.service.CVECheckService.batchGetCVEIssues(CVECheckService.java:171)
at com.microsoft.azure.toolkit.intellij.appmod.javaupgrade.service.JavaUpgradeIssuesDetectionService.getCVEIssues(JavaUpgradeIssuesDetectionService.java:385)
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 at CVECheckService.retrieveVulnerabilityData line 312 and trace its callers through fetchCves and getCveUpgradeIssues. The report provides no reproduction steps, expected behavior, or named test, so clarify how connection-reset failures should be handled before choosing a change; done should include a verified error path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, java
- Domain
- api, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100