-
Notifications
You must be signed in to change notification settings - Fork 554
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
Use ollama and deepseek-r1:1.5b can't generate graph #1123
Comments
Similar issue using locally host Ollama. |
Currently, the DeepSeek LLM model is not producing structured output as expected when used with LLM Graph Builder. We are actively investigating this issue and working on a resolution. We appreciate your patience and will provide updates as we make progress. |
@kaustubh-darekar has the problem already solved?looking forward your reply. |
Hi @jinshuaiwang , we havent found a solution yet but you can try let us know if it works. |
@kaustubh-darekar I run ollama locally,use ChatOllama and OllamaEmbeddings, when run 'docs = doc_retriever.invoke({"messages": messages}, {"callbacks": [handler]})' this line,Error retrieving documents: {code: Neo.ClientError.Statement.ParameterMissing} {message: Expected parameter(s): embedding} raise this error,what‘s the problem,how can i solve it? |
Check langchain_neo4j version you are using. with latest version embeddings are changed to query_vector |
@kaustubh-darekar Thanks a lot, I will try |
@jinshuaiwang Let me know if you have any updates. I'm currently trying to run the app locally with Ollama, but I'm running into some issues. If you manage to get it working or already have a working setup, would you mind sharing your .env files for both the frontend and backend? I'm a bit confused because there are several different answers in past discussions, and it's not entirely clear how the LLM_MODEL_CONFIG_... should be structured with Ollama. Thanks a lot in advance! |
The error occurs in the
langchain_experimental/graph_transformers/llm.py aprocess_response
function.How to fix it ?
The text was updated successfully, but these errors were encountered: