-
Notifications
You must be signed in to change notification settings - Fork 10.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
Llava 1.6: server not decoding images, but works via CLI #5515
Comments
Seems possibly related to #5514, but that's pure speculation |
yes it's the same, I responded with what needs to be done there |
Thanks for the thorough explanation in that issue, @cmp-nct. I'll close this issue out since it's a duplicate of that one. |
Opening this back up. After seeing the conversation develop in the other ticket, that issue seems to stem from differences in the system prompt between the CLI and server. But this error seems to appear while the server is loading the Base64 image into clip. Also, AFAICT this error doesn't seem to touch I haven't made much progress with debugging (unfamiliar with C++), but I'll see if I can dive in a bit deeper over the next day or two. |
Is the base64 you're putting in valid? At first I used an online converter and got the same result as you. Then I pushed the image through the This gist is what I used: https://gist.github.com/cjpais/6b7b620d29b4a8e6ca81eb5b87371bb5 |
First, let me say that I really appreciate all the work you guys are putting into llama.cpp -- it's really impressive.
I'm testing out yesterday's release of llava 1.6 (thanks so much for working on that tricky PR, @cmp-nct), and it's working well via the CLI, but when I run it via the server I'm seeing the below when it receives a request:
How I'm running via CLI (works)
How I'm running via Server (doesn't work)
To start the server:
The request I'm sending:
BASE64_IMG is the base 64 of the below image
Details
mistral-7b-q_5_k.gguf
mmproj-mistral7b-f16.gguf
4524290e87b8e107cc2b56e1251751546f4b9051
The text was updated successfully, but these errors were encountered: