mengzhx/deepseek-harness
1
0
Fork 0
mirror of https://github.com/deepseek-ai/deepseek-harness.git synced 2026-09-11 04:00:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(code-runtime-python): correct the sink comment and register the frame parse cap

Browse Source 
The review's remaining warning: the _run binding comment claimed the log sink
went 'through the bound send', contradicting the sink's actual direct use of the
bound encode+write primitives. The comment now states that; the settlement note
(en + zh) registers FRAME_PARSE_CAP_BYTES and the 65 MiB-frame regression case.
Pairing re-recorded.
This commit is contained in:
Chinesezjc
2026-08-31 14:52:01 +08:00
committed by Tianyi Cui
parent fca41b78ea
commit d90155714b
4 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/code-runtime/code-runtime-python/py/bootstrap.py
+2 -1
View File
@@ -950,7 +950,8 @@ async def _run(channel: ProtocolChannel) -> None:
# `_encode_json_plain` (module global) and `self.write_encoded` (class
# attribute) at call time, so a program rebinding either before the first
# binding call could turn a legitimate call into an exception. dispatch
# writes through these directly, and the log sink through the bound send.
# and the log sink both write through these directly (the sink does NOT go
# through send_sync, whose body resolves the same names at call time).
_write_encoded_cls = channel.write_encoded
_encode_plain_cls = _encode_json_plain
# 1. Boot handshake.