CommandCodeAI / CommandCodeAI/command-code

GLM 5.3 Flash not receiving arguments or stream ended

Aberta
#791 1 comentário 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Linguagem predominante
Sem dados de linguagem
Estrelas
4k
Forks
350
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

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
  1. Choose GLM 5.3 Flash as model
  2. Produce something with it that it almost reached 80-90K context
  3. 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

Guia de contribuição

Nenhum guia de contribuição indexado para este repositório

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Direção de pesquisa

Comece reproduzindo o problema com GLM 5.3 Flash próximo ao intervalo de contexto relatado de 80–100K usando Command Code 1.44.0 no Linux. Compare os argumentos bash vazios repetidos e a ausência de finish_reason na mudança de plano relatada, e considere a issue concluída quando as chamadas de ferramentas receberem argumentos válidos e os streams terminarem normalmente sem exigir auto-compact.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Domínio
ai, cli
Tipo de issue
Bug
Dificuldade
4/5
Tempo estimado
3-5 dias
Status de atividade
Ativa
Clareza
Razoavelmente clara
Facilidade para iniciantes
48/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.