-
Notifications
You must be signed in to change notification settings - Fork 179
Fix: Persist ChatMemory when Tool ReturnBehavior is IMMEDIATE (#2017) #2025
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
base: main
Are you sure you want to change the base?
Conversation
…verse#2017) Signed-off-by: codesmith25103 <[email protected]>
|
It would be awesome if we could have a test for this |
|
Hey @geoand I was trying to write test case but facing some difficulty in doing so, can you guide me little so I can successfully implement it. |
|
|
However, when I ran the test case after building the project, it still failed. |
|
Did you try debugging it? |
| committableChatMemory.add(toolResult); | ||
| } | ||
| if (immediateToolReturn) { | ||
| committableChatMemory.commit(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we commit the messages after the type-check in the next 3 lines?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that probably makes sense
|
Hi @codesmith25103, Do you want to try it and update your PR? Or should I create a new fork and PR? |
|
@stanlayze thanks for your help. Yes , I will try and update my PR ASAP. |
Uh oh!
There was an error while loading. Please reload this page.