mirror of
https://github.com/deepseek-ai/deepseek-harness.git
synced 2026-09-07 04:10:42 +00:00
Chinesezjc
fca41b78ea
The review found the 64 MiB parse cap contradicted the load-time budget bound: maxLogBytes/maxValueBytes could be configured up to ceiling - envelope (~256 MiB), but the receive path silently dropped any frame past the 64 MiB parser cap, so an honest child's budget-internal done frame under such a config would be discarded and the run stranded to the wall clock. The load bound is now parse-cap - envelope, so a configured budget always fits through the parser; the boundary test moves to 64 MiB - 64. The >64 MiB model-constructed binding-argument drop is registered as an accepted residual in the README (en + zh).
7 lines
451 B
YAML
7 lines
451 B
YAML
# Bilingual-pair consistency record (docs/i18n/README.md): the git blob hash of each
|
|
# side as of the last confirmed-consistent state. Both languages carry equal authority;
|
|
# after editing either side, bring the other along and re-record with:
|
|
# pnpm run verify-translation-pairing --write packages/code-runtime/code-runtime-python/README.md
|
|
README.md: 63fd9c5b03361a1970730cbf402daf5761ea7dc4
|
|
README.zh.md: 8c0d119de131cba93224a81f7d3267daec7c8bd3
|