Feat: sync test to dev #375
Merged
Conversation
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
* add: change deafult pre_load * fix: code --------- Co-authored-by: CaralHsi <caralhsi@gmail.com>
* feat: update laod cubes * fix: code format
## Description reoganize prompt with reference in user content <!-- Please include a summary of the changes below; Fill in the issue number that this PR addresses (if applicable); Fill in the related MemOS-Docs repository issue or PR link (if applicable); Mention the person who will review this PR (if you know who it is); Replace (summary), (issue), (docs-issue-or-pr-link), and (reviewer) with the appropriate information. 请在下方填写更改的摘要； 填写此 PR 解决的问题编号（如果适用）； 填写相关的 MemOS-Docs 仓库 issue 或 PR 链接（如果适用）； 提及将审查此 PR 的人（如果您知道是谁）； 替换 (summary)、(issue)、(docs-issue-or-pr-link) 和 (reviewer) 为适当的信息。 --> Summary: (summary) Fix: #(issue) Docs Issue/PR: (docs-issue-or-pr-link) Reviewer: @(reviewer) ## Checklist: - [ √] I have performed a self-review of my own code | 我已自行检查了自己的代码 - [ √] I have commented my code in hard-to-understand areas | 我已在难以理解的地方对代码进行了注释 - [ √] I have added tests that prove my fix is effective or that my feature works | 我已添加测试以证明我的修复有效或功能正常 - [ √] I have created related documentation issue/PR in [MemOS-Docs](https://github.com/MemTensor/MemOS-Docs) (if applicable) | 我已在 [MemOS-Docs](https://github.com/MemTensor/MemOS-Docs) 中创建了相关的文档 issue/PR（如果适用） - [ √] I have linked the issue to this PR (if applicable) | 我已将 issue 链接到此 PR（如果适用） - [ √] I have mentioned the person who will review this PR | 我已提及将审查此 PR 的人
…ode structure of temporal locomo.
* milvus implement * milvus implement * milvus implement --------- Co-authored-by: yuan.wang <yuan.wang@yuanwangdebijibendiannao.local>
* feat: add server api prd * feat: update memcube for api * feat: add run server api md and change user_id to user_id * fix: code format * fix:code * fix: fix code format * feat: remove ids * fix: working ids
…not completed yet; revise the feat of multiple-thread task race for scheduler dispatcher, and add multi-thread task running functions to dispatcher.
* feat: add server api prd * feat: update memcube for api * feat: add run server api md and change user_id to user_id * fix: code format * fix:code * fix: fix code format * feat: remove ids * fix: working ids * feat: add_memreader config and change neo4j db user_name
…nment variables, refactor AuthConfig and EnvConfigMixin for improved robustness and smarter configuration handling, and allow the mem scheduler to initialize modules with RabbitMQ support.
* feat: add server api prd * feat: update memcube for api * feat: add run server api md and change user_id to user_id * fix: code format * fix:code * fix: fix code format * feat: remove ids * fix: working ids * feat: add_memreader config and change neo4j db user_name * feat: add chat model
- Add RunningTaskItem schema with optional messages field in task_schemas.py - Update dispatcher to pass messages when creating RunningTaskItem instances - Enhance dispatcher_monitor to log messages info for stuck tasks (count + first 3 messages) - Add comprehensive unit tests for new messages functionality - Fix existing test assertions to handle dispatcher's message grouping logic This improvement provides better debugging visibility for stuck tasks by including the actual message content and count in monitoring logs.
Add scheduler_startup_mode configuration with STARTUP_BY_THREAD/STARTUP_BY_PROCESS constants. Supports both thread and process-based message consumption with comprehensive tests and graceful error handling.
* fix: format (#341) * change version to 1.1.0 * change: version to v1.1.1 * feat: add memory size in product api (#348) * feat: add memory size config in product api * fix: memory_size config bug * Fix/remove bug (#356) * fix: nebula search bug * fix: nebula search bug * fix: auto create bug * feat: add single-db-only assertion * feat: make count_nodes support optional memory_type filtering * fix: dim_field when filter non-embedding nodes * feat: add optional whether include embedding when export graph * fix[WIP]: remove oldest memory update * feat: modify nebula search embedding efficiency * fix: modify nebula remove old memory * Fix/api client (#357) * fix: api client get_message models * fix: format error --------- Co-authored-by: chunyu li <78344051+fridayL@users.noreply.github.com> Co-authored-by: harvey_xiang <harvey_xiang22@163.com> Co-authored-by: CaralHsi <caralhsi@gmail.com> * fix: remove old mem (#361) * feat: only single-db mode in nebula now; modify index gql for better efficiency (#363) * feat: only single-db mode in nebula now; modify index gql for better effciency * feat: delete multi-db nebula example * fix:code ci * fix:code ci * fix: nebular bug --------- Co-authored-by: CaralHsi <caralhsi@gmail.com> Co-authored-by: HarveyXiang <harvey_xiang@163.com> Co-authored-by: harvey_xiang <harvey_xiang22@163.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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
Summary: (summary)
Fix: #(issue)
Docs Issue/PR: (docs-issue-or-pr-link)
Reviewer: @(reviewer)
Checklist: