Observed on 0.14.0 (acp-core / acp-test).
On a CPU-saturated machine (shared CI runners, or locally under taskset -c 0), AcpSyncClient.prompt(...) never returns: it blocks for the entire configured requestTimeout, then fails with a Reactor timeout (FluxTimeout).
Trigger: more than one prompt on the same session. Single-prompt exchanges always pass; the second or third prompt is the one that wedges.
Repro: AcpSyncAgent + AcpSyncClient over InMemoryTransportPair, one session, three sequential prompts, run with CPUs restricted (taskset -c 0). Passes instantly on an idle multi-core box.
Observed on 0.14.0 (acp-core / acp-test).
On a CPU-saturated machine (shared CI runners, or locally under
taskset -c 0),AcpSyncClient.prompt(...)never returns: it blocks for the entire configuredrequestTimeout, then fails with a Reactor timeout (FluxTimeout).Trigger: more than one
prompton the same session. Single-prompt exchanges always pass; the second or third prompt is the one that wedges.Repro:
AcpSyncAgent+AcpSyncClientoverInMemoryTransportPair, one session, three sequential prompts, run with CPUs restricted (taskset -c 0). Passes instantly on an idle multi-core box.