fix: component_init initialize scheduler every time#915
Merged
CaralHsi merged 7 commits intoMemTensor:dev-20260119-v2.0.3from Jan 21, 2026
Merged
fix: component_init initialize scheduler every time#915CaralHsi merged 7 commits intoMemTensor:dev-20260119-v2.0.3from
CaralHsi merged 7 commits intoMemTensor:dev-20260119-v2.0.3from
Conversation
glin93
approved these changes
Jan 20, 2026
… fast search when api_module is None
glin93
approved these changes
Jan 20, 2026
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
fix: component_init initialize scheduler every time
Summary: (summary)
This PR addresses two main issues related to scheduler initialization and Redis dependency:
init_serverincomponent_initto only initialize the Redis client whenMEMSCHEDULER_USE_REDIS_QUEUEis explicitly enabled. Previously, it would attempt to initialize Redis unconditionally, which could cause issues in environments without Redis.mix_search_memoriesto check if the Redis queue is enabled. If Redis is not configured, the scheduler now gracefully degrades to fast search mode (skipping history reranking and async updates) instead of throwing an error when attempting to access the uninitialized Redis module.Fix: #(issue)
Docs Issue/PR: (docs-issue-or-pr-link)
Reviewer: @(reviewer)
@glin93
Checklist: