AI模型minimax-m2:cloud无法通过py调用
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10.5k
- Forks
- 1.2k
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
我在使用py调用minimax-m2:cloud时遇到一个问题,表现为:在ollama服务开启、网络正常、其他的云模型(如deepseek-v3.1:671b-cloud)可调用的情况下,py脚本出现以下错误:
Traceback (most recent call last):
File "d:\date\2\ai\test\BSp-test.py", line 35, in
resp_prime=ollama.chat(model="minimax-m2:cloud",messages=messages)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\date\2\python3.12\Lib\site-packages\ollama_client.py", line 365, in chat
return self._request(
^^^^^^^^^^^^^^
File "D:\date\2\python3.12\Lib\site-packages\ollama_client.py", line 189, in _request
return cls(**self._request_raw(*args, **kwargs).json())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\date\2\python3.12\Lib\site-packages\ollama_client.py", line 133, in _request_raw
raise ResponseError(e.response.text, e.response.status_code) from None
ollama._types.ResponseError: Internal Server Error (status code: 500)
ollama服务控制台出现以下内容:
[GIN] 2025/12/05 - 22:18:12 | 500 | 321.4328ms | 127.0.0.1 | POST "/api/chat"
请问这个问题如何解决?我是否应该向ollama提交issues反馈此问题?
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
Start with the reproduction in BSp-test.py, especially the ollama.chat call using minimax-m2:cloud, and compare it with the working cloud model. Run the script while monitoring the Ollama service and its POST /api/chat request, then use the server response and traceback to isolate the 500 error. Done means identifying a reproducible client or service defect and documenting the evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ollama, python
- Domain
- ai, api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100