fix: add read-after-write retries and cleanup to prevent temp memory leaks #828
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.
…leaks
Description
Summary:
This PR hardens the mem_read pipeline against read-after-write inconsistencies in GeneralScheduler._process_memories_with_reader . It adds a small retry loop when fetching newly-written memory nodes and introduces a best-effort cleanup path (delete + refresh) when the nodes still cannot be retrieved, preventing temporary memories from being leaked due to early returns.
Fix: #(issue)
Docs Issue/PR: (docs-issue-or-pr-link)
Reviewer: @(reviewer)
Checklist: