lmstudio-ai / lmstudio-ai/mlx-engine

Failed to run deepseek-ocr model by api(/v1/chat/completion)

Open
#244 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.2k
Forks
133
Avg merge
21h 6m
Merged PRs (30d)
1

Description

LM Studio 0.3.31 build7
MLX version info:
- mlx-engine==c7cedfa
- mlx==0.29.3
- mlx-lm==0.28.4
- mlx-vlm==0.3.5

Run deepseek-ocr model by api(/v1/chat/completion), request with only one image and one text message
- in stream mode, error: TypeError: object of type 'NoneType' has no len()
- in none stream, error: Channel Error
```
2025-11-21 15:25:03 [INF0l Returning "data":["id":"deepseek-ocr","object":"model","owned by":"organization owner"object":"list"]
2025-11-21 15:26:41[INFO] [LM STUDI0 SERVER] Running chat completion on conversation with 2 messages.2025-11-21 15:26:41[LM STUDI0 SERVER]Streaming response...[INFO]
2025-11-21 15:26:41[ERROR] Error in iterating prediction stream: TypeError: object of type 'NoneType' has no len(). Error Data:n/a,Additional Data:n/a
2025-11-21 15:37:13[INFO] ILM STUDI0 SERVER] Running chat completion on conversation with 2 messages.
2025-11-21 15:37:13[ERROR]Error:Channel Error
2025-11-21 15:38:42[INF0] Server stopped.
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the deepseek-ocr request through the /v1/chat/completion entry point using one image and one text message, with streaming enabled and disabled. Trace the failure reported as a NoneType length error in stream mode and a Channel Error otherwise. Done means both request modes return a successful completion.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.