Fix scheduler memory get with user_name and retries#624
Merged
Conversation
tangg555
approved these changes
Dec 5, 2025
Correctly pass mem_cube_id as user_name to get_working_memory in process_session_turn to maintain tenant isolation for working memory management. This addresses a potential data leakage issue in multi-tenant environments.
tianxing02
pushed a commit
to tianxing02/MemOS
that referenced
this pull request
Feb 24, 2026
* Fix scheduler memory get with user_name and retries * Fix: Ensure multi-tenancy for working memory in GeneralScheduler Correctly pass mem_cube_id as user_name to get_working_memory in process_session_turn to maintain tenant isolation for working memory management. This addresses a potential data leakage issue in multi-tenant environments. * Revert user_name param on mem_os core accessors --------- Co-authored-by: glin1993@outlook.com <>
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
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
Summary: (summary)
Fix: #(issue)
Docs Issue/PR: (docs-issue-or-pr-link)
Reviewer: @(reviewer)
Checklist: