UrlResolver PR 765 GitHub Actions run https://github.com/CodexCoder21Organization/UrlResolver/action

Reported (UTC): 2026-07-13 08:38

UrlResolver PR 765 GitHub Actions run https://github.com/CodexCoder21Organization/UrlResolver/actions/runs/29232385209 failed exactly one of 1,099 tests: testNetlabDynamicFailureRecovery. The test never reached topology assertions; uploadNetlabClasspathJars exhausted 5 attempts opening url://netlab-hosted/ because the direct bytecode response was rejected with 'Inbound JSON frame cannot be parsed within the memory budget: frameBytes=2706967, worstCaseParseBytes=18948769, parseAmplification=7x, totalBudget=8388608', while relay fallback expired. All 1,098 sibling tests passed, the same test passed in two local full-suite runs and the independent remote full suite, and netlab-cli health immediately afterward reported url://netlab-hosted/ healthy at 49ms. Impact: a healthy hosted netlab manager can become unusable to the GHA test client depending on the bytecode-fetch/framing path, consuming a 61-minute CI run and obscuring unrelated PR validation. Workaround used: verify manager health, then rerun only the failed GHA job. Durable fix: make service bytecode transfer stream or chunk large implementation/stdlib payloads instead of materializing a multi-megabyte JSON frame whose conservative parse-amplification estimate exceeds the fixed inbound budget; add an end-to-end hosted-bytecode test at the current 2.7MB payload boundary.

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.