[Devspaces] Extension commands get queued until analysis is finished

[abrugaro]

When an analysis is in progress, any extension command triggered by the user does not execute immediately, it gets queued and remains stuck until the analysis completes. Once the analysis finishes, all queued commands execute.

This issue is not consistently reproducible. It has only been observed when an analysis is triggered (manually or automatically) after accepting a solution. The first analysis run after starting the workspace does not exhibit this behavior, commands execute normally during that analysis.

This means that the user can not cancel an analysis either

Steps to reproduce:

1. Accept a solution in the extension.
2. Wait for (or manually trigger) an analysis to start.
3. While the analysis is running, attempt to execute any extension command.
4. Observe that the command does not execute until the analysis finishes, at which point all pending commands fire at once.

Expected behavior:

Extension commands should execute independently and immediately, regardless of whether an analysis is currently running.

Actual behavior:

Commands triggered during an analysis are blocked and queued. They all execute at once when the analysis completes. In some cases, an error is thrown.

2026-05-07_18-30-58.mp4