While repeatedly running a single UrlResolver test with jars/KompileCli.jar 0.0.77, a warm

Reported (UTC): 2026-07-14 10:47

While repeatedly running a single UrlResolver test with jars/KompileCli.jar 0.0.77, a warm build-cache invocation hung for more than four minutes before launching any BootstrapRunner worker. jcmd Thread.print showed main parked in kompile.WorkspaceKt.unifiedResolve -> coursier.Fetch.fetch and coursier-pool-1-thread-7 blocked in HttpsURLConnection.connect via CacheUrl.redirect/Downloader.remote. The requested artifacts were already cached and prior identical selected-test invocations had succeeded. Despite HOME=/code/fix-deepmap/home and JAVA_OPTS=-Duser.home=/code/fix-deepmap/home, the launcher process classpath was populated from /home/leslie/.cache/coursier, so the documented isolated-HOME pattern did not isolate all Coursier state. Impact: two otherwise valid stress attempts never reached their invocation marker within 60s/300s, and an unconstrained verification was blocked until manually diagnosed. Workaround: cancel only the pre-test fetch and set COURSIER_MODE=offline after the first successful cache fill. Durable fix: Kompile should honor an explicit isolated Coursier cache throughout launcher and unifiedResolve, avoid remote fetches for fully cached coordinates, and apply bounded connect/read deadlines with a diagnostic naming the URL rather than silently parking selected-test startup.

Production verification — 2026-07-17

Status: STILL EXISTS. A live ProductionHealth URL connection succeeded but emitted repeated NothingToCompleteException failures while forwarding gossip; the last HardwareControlFabric daemon log also contains Netty ByteBuf leak reports in libp2p negotiation paths.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.