Repository navigation
Replies: 1 comment
|
Workaround available for this one. I hit it while running Auto review against an always-thinking model (the review was dispatched with the catalog default What it changes for this report: the review request now carries the session's reasoning level, plus a configurable fallback level that is capability-checked against the review route before it is sent. If the review route is pinned to a model that cannot take the session's level, the review retries once without the level instead of failing every call of that session (fail-closed is preserved: a review that still fails denies the call). Also in the same plugin (the #8764 half): the request carries Extra: a per-session reviewer-model picker — review with a different model than the one under review, stored per session, resettable to "follow the session model". Install (dsh then restart Disclosure — please read before installing:
Repo + design notes: https://github.com/DMIAOCHEN/dsh-auto-review-plus |
Uh oh!
There was an error while loading. Please reload this page.
环境
0.2.0-rc.2(npx -y @deepseek-ai/dsh web;registry 的latest与next均为此版本,无可升级修复)@deepseek-ai/dsh-experimental-auto-review0.2.0-rc.2(web profile,已启用,/permission auto)zai,modelglm-5.3-flash(智谱"始终思考"模型,仅接受 low/high/max 思考级别)现象
开启 Auto review 后,每次工具调用(原生与 PTC 内层)都失败:
失败即 fail-closed:工具体不执行。Auto 模式在该模型路由下完全不可用。
根因链
packages/experimental/auto-review/src/index.ts的classifyRisk()构造审查请求时,GenerateOptions只包含provider/model/system/messages/temperature: 0/signal—— 没有携带任何 reasoning 级别(也没有沿用当前会话请求的思考级别)。packages/llm/llm-pi-ai/src/adapter.ts的解析回退是options.reasoningEffort ?? profile.reasoning;provider profile 未配置reasoning字段时两者均为undefined,reasoning 选项被整体省略。@earendil-works/pi-ai@0.87.1)对带 reasoning 元数据的目录模型在无显式级别时套用自己的缺省级别,在线上载荷中变成了显式的thinking关闭参数。注意这与 adapter 现有注释自述的语义相悖(
profileOptions对off的处理):"Omittingreasoningentirely ... a provider whose own default is to think would keep thinking" —— 省略 reasoning 本应让 provider 端用自己的默认(对 GLM 即保持思考),但 pi-ai 对目录 reasoning 模型的缺省分发实际发送了 disable。主对话不受影响的原因:会话请求携带用户在模型选择中显式指定的思考级别,只有审查请求落到"缺省"路径。
期望行为 / 建议修复(按优先级)
临时绕过(供其他用户参考)
reasoning: low(provider 级字段;审查请求的回退值会变成 low,API 明确接受 low/high/max;主对话的显式级别优先,不受影响);感谢!Auto review 本身的设计(审查请求不干预思考配置)是对的,问题出在缺省分发这一层,期待修复。
All reactions