Progress notification never resolves if Library Manager search used during library installation

[luqizhi666]

Describe the problem

Use of the Library Manager search functionality while library installation is in progress results in the installation progress notification never completing:

To reproduce

1. Select Sketch > Include Library > Manage Libraries... from the Arduino IDE menus to open the "Library Manager" view in the left side panel.
2. Scroll down through the list of libraries until you see any entry for a library that is not yet installed.
3. You will see an "INSTALL" button at the bottom of the entry. Click the button.
   A notification will appear at the bottom right corner of the Arduino IDE window to indicate that installation of the library is in progress.

   ⓘ Successfully installed library ...

4. While the installation is still in progress, type any query in the "Filter your search..." field of the "Library Manager" view.
   🐛 The list of libraries is not updated to those matching the search query.
5. Wait for the notification to indicate the library installation has completed (i.e., "ⓘ Successfully installed library ...".
   🐛 The library installation process never completes.

Expected behavior

It is possible to perform other operations in Library Manager while an installation is in progress.

- OR -

If it is not possible perform other operations in Library Manager while an installation is in progress the application should show the installation progress in a modal window so that the user is blocked from breaking the IDE by triggering impossible concurrent operations.

Arduino IDE version

Original report

2.3.3

Last verified with

c09b5f7

Operating system

Windows

Operating system version

• Windows 10
• Windows 11

Additional context

The fault does not occur when the equivalent procedure is performed using Boards Manager.

Additional Reports

• https://forum.arduino.cc/t/board-manager-not-filtering/1327528

Issue checklist

• I searched for previous reports in the issue tracker
• I verified the problem still occurs when using the latest nightly build
• My report contains all necessary details