-
Notifications
You must be signed in to change notification settings - Fork 2.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]: Fail to bind LLM used by RAPTOR #4126
Comments
### What problem does this PR solve? #4126 ### Type of change - [x] Bug Fix (non-breaking change which fixes an issue)
It's ok now with the nightly. Tanks. |
For 3/51 documents I always get a RAPTOR error, but if I relaunch in UI, keeping the chunks already calculated (not clear existing chunks), it manages to finish and the document goes to success status. unfortunately, as I've launched about twenty simultaneous parse operations, I can't find the console logs for sure. For 1/51 it's not working (Rapport 2005_I.pdf)
log console
Thanks for your great work |
@KevinHuSh Hi, I'm still having this issue in 0.15.1. When I use Ollama (llama3.1), but also when I use Together.ai LLM (llama 3.3) it has the same issue |
@KevinHuSh This is still a bug for me in 0.15.1 using either Ollama or Together.ai as an inference server. 2025-01-20 13:31:37,682 INFO 17 HTTP Request: POST http://ollamainference:11434/v1/chat/completions "HTTP/1.1 200 OK" |
Ollama seems have this kind of issue here. |
I tried it with Together.ai with llama3.3, the same thing happens. |
Is there an existing issue for the same bug?
RAGFlow workspace code commit ID
8939206
RAGFlow image version
v0.15.0-slim
Other environment information
Actual behavior
I use version 0.15.0-slim with local Ollama for embedding (snowflake-arctic-embed2) and LLM (qwen2.5:14b) with success for parse.
If I activate RAPTOR for a knowledge base, I get an error and Fail parsing :
logs:
My Ollama local LLM I'm using for RAPTOR isn't compatible ? or other bug / problem ?
Thank's for your great work.
Expected behavior
No response
Steps to reproduce
Additional information
No response
The text was updated successfully, but these errors were encountered: