GoogleCloudPlatform/kubectl-ai

stream model will report simulated streaming failed during non-streaming call

Open

#166 opened on May 8, 2025

View on GitHub
 (15 comments) (0 reactions) (0 assignees)Go (708 forks)auto 404
good first issue

Repository metrics

Stars
 (7,532 stars)
PR merge metrics
 (PR metrics pending)

Description

as below `[root@k8s-test ~]# kubectl-ai --llm-provider=openai --model=qwen3-235b-a22b

Hey there, what can I help you with today?

show me all deployment in the deafult namespace E0508 11:30:21.562983 32248 openai.go:249] OpenAI ChatCompletion API error: POST "https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions": 400 Bad Request {"code":"invalid_parameter_error","param":null,"message":"This model only support stream mode, please enable the stream parameter to access the model. ","type":"invalid_request_error"} Error: simulated streaming failed during non-streaming call: OpenAI chat completion failed: POST "https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions": 400 Bad Request {"code":"invalid_parameter_error","param":null,"message":"This model only support stream mode, please enable the stream parameter to access the model. ","type":"invalid_request_error"}

exit [root@k8s-test ~]# kubectl-ai --llm-provider=openai --model=qwen-plus

Hey there, what can I help you with today?

show me all deployment in the deafult namespace Running: kubectl get deployments -n deafult`

Contributor guide

Research direction
Inspect the simulated streaming logic in the OpenAI client code. Identify where non streaming calls are wrapped and ensure models that require stream mode are handled correctly by either forcing streaming or falling back properly.
Tech stack
go
Domain
backendcliai
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoLLM API basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50