microsoft / microsoft/azure-tools-for-java

[IntelliJ] Uncaught Exception Operator called default onErrorDropped reactor.core.Exceptions$ErrorCallbackNotImplemented: java.util.concurrent.TimeoutException: Did not observe any item or terminal signal within 10000ms in 'subscribeOnCallable' (and no fal

Open
#12,166 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.3 IU-261.25134.95
OS: Windows 11
JDK: JetBrains s.r.o. 25.0.3
Plugin version: 3.97.6-2026.1
Additional Info: None
Parent component:

com.intellij.openapi.wm.impl.IdeRootPane[,8,8,2560x1392,invalid,layout=com.intellij.openapi.wm.impl.IdeRootPane$CustomHeaderRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]

Error message:

IdeaLoggingEvent[message=Operator called default onErrorDropped, throwable=reactor.core.Exceptions$ErrorCallbackNotImplemented: java.util.concurrent.TimeoutException: Did not observe any item or terminal signal within 10000ms in 'subscribeOnCallable' (and no fallback has been configured)
Caused by: java.util.concurrent.TimeoutException: Did not observe any item or terminal signal within 10000ms in 'subscribeOnCallable' (and no fallback has been configured)

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 by reproducing the report in IntelliJ IU-261.25134.95 on Windows 11 with JDK 25.0.3 and plugin 3.97.6-2026.1. Trace the source of the Reactor timeout in the IntelliJ plugin and identify which operation emits the dropped error. Done means the reported uncaught exception no longer occurs or has a confirmed, testable handling path.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
desktop, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.