Compile actions intermittently blocked/slow since v3 update

Type: Bug

Since the v3 update, I've noticed that compile actions (defined through actions.json) sometimes hang or take much longer than expected when working in a local repository.

The issue is intermittent, but it seems to happen when other extension activity is running on the same connection `see Output(Code for i)`

This one took 8 mins.

This in my opinion is happening if the extension is fetching metadata for object browsing, library lists, the IFS Browser, or Environment views while I trigger a compile, the compile can be delayed significantly.

Before v3, compile operations appeared to run independently of other extension activity. Since the database access layer changes in v3, that no longer seems to be the case. Looking through the code, I noticed the introduction of ileQueue, which appears to queue database requests. My suspicion is that if there are already queries in the queue, compile-related work has to wait behind them, which can lead to unpredictable delays.

Steps to Reproduce

- Connect to an IBM i system.
- Open the Object Browser, IFS Browser, or Environment view.
- Trigger a refresh or expand a library containing a large number of objects or members.
- While that operation is still running, trigger a compile action on a source in local repo.
- Observe that the compile may take significantly longer than expected, or appear to hang, compared to running the same compile when no background browsing activity is occurring.

Extension version: 3.0.12
VS Code version: Code 1.132.0 (df53daabb18cd157bdb08c7f01c34df936cf12f4, 2026-08-04T15:30:20Z)
OS version: Windows_NT x64 10.0.26200
Modes:

System Info

|Item|Value|
|---|---|
|CPUs|11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 x 2419)|
|GPU Status|2d_canvas: enabled
GPU0: VENDOR= 0x8086, DEVICE=0x9a49 [Intel(R) Iris(R) Xe Graphics], DRIVER_VENDOR=Intel, DRIVER_VERSION=31.0.101.5522 *ACTIVE*
GPU1: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VERSION=10.0.26100.8521
Machine model name:
Machine model version:
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
trees_in_viz: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgpu: enabled
webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|15.79GB (2.96GB free)|
|Process Argv|--crash-reporter-id f9079462-9b9b-4991-b9a7-3822cddb1673|
|Screen Reader|no|
|VM|0%|

A/B Experiments

```
vsliv368:30146709
vswsl492:30256859
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31463988
aj953862:31281341
82j33506:31327384
envsactivate1:31551504
cloudbuttont:31379625
42190218_ostrepl:31403339
ec5jj548:31422691
cp_cls_t_966_ss:31526232
4je02754:31466945
8hhj4413:31478653
cp_cls_c_1081:31454833
conptydll_true:31498968
e9c30283:31461165
test_treatment2:31471001
c9b86496:31447327
capico_axe_098a3278:31555651
ei9d7968:31496641
chat:31457767
8hig5102:31480529
89g7j272:31518289
i2gc6536:31499202
52612955:31516516
ghj88844:31499326
ddid_t:31478206
hmra_i5g22:31518061
7df3h592:31512476
cp_cls_t_1082:31535311
logging_enabled_new:31498466
db5d2638:31499441
jb_cp_cls_t_632:31543129
56dj4588:31512888
32d76977:31512328
ha629193:31508444
a1ije391_t:31540920
jbcp_cls_pctr_t:31531130
61138546:31518536
cp_intellij_t_nes:31548657
d7b18187:31526828
ahp-both-windows:31556933
session_8:31532895
ihg5j128:31534457
f412h606:31551416
9gg7f176:31542112
nes-ex-cf-euporie-03:31542868
enable_editor_pane_layout:31569726
allow-none:31555437
6i51c363:31551401
36h42362:31564511
c7c27ce7:31554789
1h923230:31564177
0dg73464:31554319
treatment-23-1:31555779
unuse_dynamic_mcp:31555281
0c1h4866:31566224
session-archive:31558132
5b8j3302:31564601
mangle-name-control:31572633

```

Start with compile actions defined through actions.json, the ileQueue introduced in v3, and the Output (Code for i) logs. Reproduce the issue by refreshing or expanding a large Object Browser, IFS Browser, or Environment view while compiling from a local repository. Done means compile actions no longer experience significant delays or apparent hangs during concurrent browsing activity.

Written by the indexing model from the issue text.