mirror of
https://github.com/deepseek-ai/deepseek-harness.git
synced 2026-09-06 07:11:59 +00:00
The reviewer's standing item: the unknown-binding reply ran JSON.stringify on the WHOLE capped target (global + '.' + name, each up to maxValueBytes code units), allocating the escaped form — up to ~6x under control-heavy input, a multi-hundred-MB spike near the maxValueBytes ceiling that no hostile-peer bound would have admitted. The escaped preview is now built from a 1 KiB prefix of the target (enough to identify the binding); capMessage still enforces the reply budget. A forged huge-name case drives the path.