Fix/281 session aware memory#292
Merged
Merged
Conversation
…o memory and register as activity Signed-off-by: Casper Nielsen <[email protected]>
Signed-off-by: Casper Nielsen <[email protected]>
…session aware Signed-off-by: Casper Nielsen <[email protected]>
Signed-off-by: Casper Nielsen <[email protected]>
CasperGN
force-pushed
the
fix/281-session-aware-memory
branch
from
December 3, 2025 22:38
3fbd03b to
d0f13f0
Compare
Member
|
@CasperGN see conflict |
Contributor
Author
|
@yaron2 merge conflict fixed |
yaron2
approved these changes
Dec 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Implement session aware handling of saving memory. This fixes the
Error when running fan-out during
run_toolor when running several invocations concurrently.Subsequently, this fix also handles the issue with concurrent invocations with fan-out
run_toolthat could result in the tool call order to be scrambled which caused issues with OpenAI.Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #281
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:
Note: We expect contributors to open a corresponding documentation PR in the dapr/docs repository. As the implementer, you are the best person to document your work! Implementation PRs will not be merged until the documentation PR is opened and ready for review.
No documentation update needed as it's compatible with the current docs.