-
Notifications
You must be signed in to change notification settings - Fork 103
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
[Question] Memory deleted at the end of the request #1232
Comments
If the AiService is request scoped (the default), we delete the memory when the request is completed. The docs provide more information |
But the AiService is an interface. I do not understand what the docs are trying to tell me here. I cannot
|
Adding |
It's just a warning, you can safely ignore it. As for the tools issue, I would need to have a reproducer that I can in order to be able to give you an answer |
https://github.com/JanHuege/MinimumReproTool/tree/main I added a few .stream.filters to remove the empty entries. What I did is I ingested a couple of .pdfs and then ran a few requests using llama 3.2 locally. I used a persistent redis and llama on my local docker instead if using the devservices. I hope this helps. |
I was expecting you to use the langchain4j ollama package internally but it seems like this is not the case. The code expects all tool-calls from the LLM response are actual tools that are available. I guess langchain4j ollama should filter these out. Also if no tool is called this should not result in empty ToolExecutionRequests I guess. I think this issue also exists in langchain4j: toToolExecutionRequests(chatResponse.getMessage().getToolCalls()) |
Nice catch! Would you like to provide a fix for this? |
I am not sure if I understand this well enough at the moment since I just started trying it out. But maybe I'll try and look into it tomorrow no guarantees. |
Created a PR @geoand . Feel free to critique. |
Hi,
I am currently experimenting with the quarkus langchain4j features and I was wondering why the memory is not working. So I decided to implement a RedisMemoryStore myself. Now it seems to be used but after each request all messages are deleted since quarkus seems to call the
deleteMessages
Method on my Implementation of ChatMemoryStoreBehavior:
Can someone explain this behavior?
The text was updated successfully, but these errors were encountered: