feat: DeepSeek Responses 严格 Schema 通道 / strict Schema transport - #69
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
摘要 / Summary
deepseek_responses_json_schema传输方式,将每个 packet 已绑定的output.schema.json直接交给 DeepSeek Responses API 的 JSON Schema 输出。deepseek_responses_json_schema, which sends the packet-boundoutput.schema.jsondirectly to DeepSeek Responses API structured output.json_schema输出格式;Responses 调用明确关闭 thinking。json_schemaformat; Responses calls explicitly disable thinking.验证 / Verification
python -m unittest tests.benchmark.core.test_model_runner— 21 passedpython scripts/run_ci_tests.py core— 482 passedData/仍由 Git ignore;本 PR 只包含公共 runner、CLI 与合成测试。隐私与范围 / Privacy and scope
Data/内容。Data/content is read, staged, or committed.限制与下一步 / Limitations and next step
参考 / Reference: DeepSeek Responses API.