lmstudio-ai / lmstudio-ai/lmstudio-bug-tracker
Local Interface Server can not work when the request content is empry
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 152
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
Local Interface Server works well in example
curl http://localhost:1234/v1/chat/completions \
-H "Content-Type: application/json" \
-d '{
"model": "lmstudio-community/Meta-Llama-3-8B-Instruct-GGUF",
"messages": [
{ "role": "system", "content": "Always answer in rhymes." },
{ "role": "user", "content": "Introduce yourself." }
],
"temperature": 0.7,
"max_tokens": -1,
"stream": true
}'
However, when the content is empty, it can not work.
I just set content to empty, it prints error.
[2024-05-04 01:10:59.564] [INFO] [LM STUDIO SERVER] Processing queued request...
[2024-05-04 01:10:59.564] [INFO] Received POST request to /v1/chat/completions with body: {
"model": "lmstudio-community/Meta-Llama-3-8B-Instruct-GGUF",
"messages": [
{
"role": "system",
"content": ""
},
{
"role": "user",
"content": "Introduce yourself."
}
],
"temperature": 0.7,
"max_tokens": -1,
"stream": true
}
[2024-05-04 01:10:59.565] [ERROR] [Server Error] {"title":"'messages' array must only contain objects with a 'content' field that is not empty"}
Just hope when role of system's content is empty, it still can work.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the POST request to /v1/chat/completions with an empty system-message content field and compare it with the working example. Trace the local interface server's validation that rejects empty message content; done means the request is accepted and processed without the reported error.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100