Repository navigation
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
WalkthroughThe change captures client reasoning effort in generated relay metadata for OpenAI chat-completions and Responses requests. Tests verify the ChangesReasoning effort capture
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: Poem
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
duplicated |
|
真巧啊,和我撞一起了 |
Important
📝 变更描述 / Description
调用日志中的推理强度此前依赖具体渠道适配器写入,因此 New API、Sub2API、Codex、高级自定义以及请求体透传等路径可能遗漏该字段。
本次改动将推理强度的采集前移到统一请求解析阶段:Chat Completions 从
reasoning_effort读取,Responses API 从reasoning.effort读取。这样日志元数据不再依赖后续选择的渠道或是否执行请求转换,同时保留渠道适配器根据模型后缀推导推理强度的现有行为。同时增加表格驱动测试,覆盖 Chat Completions 与 Responses API 两种请求格式。
🚀 变更类型 / Type of change
🔗 关联任务 / Related Issue
✅ 提交前检查项 / Checklist
Bug fix,我已提交或关联对应 Issue,且不会将设计取舍、预期不一致或理解偏差直接归类为 bug。📸 运行证明 / Proof of Work
go test ./...全部通过。/v1/chat/completions,请求携带reasoning_effort: "high",响应成功且 UI 日志正确显示推理强度。/v1/responses,使用glm-5.2和reasoning.effort: "high",返回 HTTP 200,消费日志中的reasoning_effort正确记录为high。Summary by CodeRabbit
New Features
Tests