CommandCodeAI / CommandCodeAI/command-code
GLM 5.3 Flash not receiving arguments or stream ended
Personne n'a encore pris cette issue.
- Langage dominant
- Aucune donnée de langage
- Étoiles
- 4k
- Forks
- 350
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
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
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par reproduire le problème avec GLM 5.3 Flash près de la plage de contexte signalée de 80–100K, en utilisant Command Code 1.44.0 sous Linux. Comparez les arguments bash vides répétés et l’absence de finish_reason au cours du changement de plan signalé, et considérez l’issue comme terminée lorsque les appels d’outils reçoivent des arguments valides et que les streams se terminent normalement sans nécessiter auto-compact.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Domaine
- ai, cli
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- Active
- Clarté
- Plutôt claire
- Accessibilité débutants
- 48/100