-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: why ollama/gemma3:27b can not execute cmd #7613
Comments
Could you perhaps tell what is the error? Alternatively, you may want to try a similar size LLM that was tuned on |
can you help me. i want to download this gguf(q4_k_m):https://huggingface.co/bartowski/all-hands_openhands-lm-32b-v0.1-GGUF/tree/main how to load this to ollama? what is the correct template to use in the Modelfile to use functions/tools successfuly? ollama sometimes doesnt like template unless its own from "ollama pull 'model'" command. maybe this is wrong repo to ask these questions? |
|
I get the following result in chat.
|
thanks. i managed to download it but then in open-hands ui it was not connecting. i had to try several options for the name of the model. it ended up working using: |
im getting similar error
and saw this in the open-hands console window, not sure what it means:
i then told it to 'continue' but i think it started to hallucinate or similar cus gpu temps went skyhigh for a while but it never returned any output. i left it for about 5mins and then killed ollama to save my gpu's life. Edits: sorry i had to edit like 10 times and this is best i could do. please don hate me im new to github :( |
Is there an existing issue for the same bug?
Describe the bug and reproduction steps
Prompt:
creat a new branch from /workspace/test name test_branch
respond:
Okay, let's create a new branch.
<function_call>
execute_command
{
"command": "git checkout -b test_branch"
}
it can not execute command.
OpenHands Installation
Docker command in README
OpenHands Version
No response
Operating System
None
Logs, Errors, Screenshots, and Additional Context
No response
The text was updated successfully, but these errors were encountered: