Chinesezjc ae8070d799 fix(code-runtime-python): stop overclaiming O(cap) object metering ...

checkDoneValue cannot bound object width sublinearly: JS has no lazy own-key
iterator (for...in materializes the key set), and done.value is already
JSON.parse'd before the check runs, so the frame's width is paid upstream. The
genuine width bound is the host's fixed 256 MiB fd-3 receive buffer (a later
stack layer). Reword the JSDoc and branch comments to claim only what holds —
the traversal caps the INCREMENTAL allocation the check would add (escaped
strings, enqueued children, per-key stringify) and refuses over-budget before
those secondary allocations — and drop the mid-count micro-check that JS cannot
honor. Replace the Proxy test (whose ownKeys allocated a 2M array, proving
nothing) with assertions that an over-budget string/array/object is refused
before its escaped copy or child enqueue.

2026-08-07 13:27:54 +08:00

..

protocol-mirror.e2e.ts

fix(code-runtime-python): close coverage gap and tighten the wire mirror

2026-08-07 13:27:54 +08:00

protocol.spec.ts

fix(code-runtime-python): stop overclaiming O(cap) object metering

2026-08-07 13:27:54 +08:00