GLM 5.3 Flash not receiving arguments or stream ended
還沒有人認領這個 Issue。
評估
研究方向
首先,在 Linux 上使用 Command Code 1.44.0,於報告的 80–100K context 範圍附近重現使用 GLM 5.3 Flash 時的問題。比較報告的計畫變更中反覆出現的空白 bash 引數和缺少的 finish_reason,並在工具呼叫收到有效引數且串流正常結束、不需要 auto-compact 時,將 issue 視為完成。
由索引模型根據 Issue 內容生成。
描述
Summary
I was trying to find alternative for dsv4f peak hours and I think GLM 5.3 flash is a good model
I was on Go model before, using 5.3 flash with no hassle, both in cmcd, opencode, pi, routed with 9router
Since my Go plan almost ended, I upgraded my plan to GOAT and started using GLM 5.3 Flash.
Weirdly, whenever the model almost reached 100K, It keep getting something like
Validation failed for tool "bash":
- command: must have required properties command
Received arguments:
{}
or
Stream ended without finish_reason
I've tried to ask dsv4f to fix this issue, most of the solution says to change the context window to somewhere between 80-90K. The solution sometimes working sometimes not that I reached annoyed state (and moved to dsv4f on peak hours 😭). I believe that this is neither the harness nor 9router's problem (also this is what ds4vf stated too). Just wondering why this happened when I switch plan and it was working fine before
Expected Behavior
GLM 5.3 Flash working fine like a few weeks ago
Actual Behavior
Weirdly, whenever the model almost reached 100K, It keep getting something like
Validation failed for tool "bash":
- command: must have required properties command
Received arguments:
{}
or
Stream ended without finish_reason
Steps to reproduce the issue
- Choose GLM 5.3 Flash as model
- Produce something with it that it almost reached 80-90K context
- The Received arguments error will continuously occurred if not auto compact
Command Code Version
1.44.0
Operating System
Linux
Terminal/IDE
Unknown
Shell
cmd.exe
Session file (optional)
No response
Fix prompt (optional)
No response
Additional context
No response
- 主要語言
- 沒有語言資料
- 星號
- 4k
- 分支
- 350
- PR 合併指標
- 30 天內沒有已合併 PR
貢獻指南
這個儲存庫沒有索引到貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
CommandCodeAI/command-code 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 68/100
CommandCodeAI/command-code#855 ·
-
難度 2/5 1-3 小時 新手友好度 78/100
CommandCodeAI/command-code#841 · 1 則留言 ·
-
難度 2/5 1-3 小時 新手友好度 68/100
CommandCodeAI/command-code#655 · 1 則留言 ·
-
難度 2/5 1-3 小時 新手友好度 68/100
CommandCodeAI/command-code#608 ·
-
難度 3/5 1-2 天 新手友好度 70/100
CommandCodeAI/command-code#893 ·
查看 CommandCodeAI/command-code 的全部 Issue
相似的 Issue
-
enhancement
難度 2/5 1-3 小時 新手友好度 68/100
JuliusBrussee/caveman#1102 · 1 則留言 ·
-
難度 2/5 1-3 小時 新手友好度 78/100
use-agent-os/agent-os#3263 ·
-
[Bug]: context-limit error parsing has no pattern for llama.cpp's "context size (N tokens)" phrasing 未關閉area/compression area/local-models area/sessions comp/agent duplicate P2 sweeper:risk-session-state type/bug
難度 2/5 1-3 小時 新手友好度 82/100
NousResearch/hermes-agent#117793 · 1 則留言 ·
-
possible bug
難度 2/5 1-3 小時 新手友好度 88/100
Mintplex-Labs/anything-llm#6415 · 1 則留言 ·
-
難度 2/5 1-3 小時 新手友好度 82/100