Skip to content

fix: recall playground memories from every searched cube - #2436

Merged
syzsunshine219 merged 2 commits into
MemTensor:dev-v2.0.36from
Wang-Daoji:fix/playground-recall-all-cubes
Sep 29, 2026
Merged

syzsunshine219 merged 2 commits into
MemTensor:dev-v2.0.36from
Wang-Daoji:fix/playground-recall-all-cubes

Conversation

@Wang-Daoji

Copy link
Copy Markdown
Collaborator

Playground only kept the first cube in text_mem, so personal memories were dropped when a knowledge-base cube came first.

Description

Please include a summary of the change, the problem it solves, the implementation approach, and relevant context. List any dependencies required for this change.

Related Issue (Required): Fixes #issue_number

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (does not change functionality, e.g. code style improvements, linting)
  • Documentation update

How Has This Been Tested?

poetry run pytest tests/api/test_playground_cube_recall.py -q
  • Unit Test
  • Test Script Or Test Steps (please provide)
  • Pipeline Automated API Test (please provide)

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 (if applicable) | 我已在 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 的人

Reviewer Checklist

  • closes #xxxx (Replace xxxx with the GitHub issue number)
  • Made sure Checks passed
  • Tests have been provided

Playground only kept the first cube in text_mem, so personal memories
were dropped when a knowledge-base cube came first.

Co-authored-by: Cursor <cursoragent@cursor.com>
@Memtensor-AI Memtensor-AI added area:api 云服务 / FastAPI / OpenAPI / MCP status:in-progress Someone or AI is working on it | 人工或 AI 正在处理 labels Sep 29, 2026
@Memtensor-AI

Copy link
Copy Markdown
Collaborator

🤖 Open Code Review

Target: PR #2436
Task: fc65e4413e41865a
Base: dev-v2.0.36
Head: fix/playground-recall-all-cubes

✅ OpenCodeReview: Review complete: 0 finding(s) across 2 selected item(s).

Generated by cloud-assistant via Open Code Review.

@Memtensor-AI

Copy link
Copy Markdown
Collaborator

✅ Automated Test Results: PASSED

All tests passed (2/2 executed). memos_python_core/changed-repo-python: 2/2. Duration: 14s

Branch: fix/playground-recall-all-cubes

@Memtensor-AI Memtensor-AI added status:ready Ready for implementation; waiting for assignee or AI dispatch | 可进入实现,等待认领或派发 and removed status:in-progress Someone or AI is working on it | 人工或 AI 正在处理 labels Sep 29, 2026
@syzsunshine219
syzsunshine219 merged commit 568e9a1 into MemTensor:dev-v2.0.36 Sep 29, 2026
18 checks passed
@endxxxx endxxxx mentioned this pull request Nov 9, 2026
4 tasks done
syzsunshine219 added a commit that referenced this pull request Nov 9, 2026
## Description

Merge `dev-v2.0.36` into `main` for MemOS v2.0.36. The final
release-branch commit sets both the package version and
`memos.__version__` to `2.0.36`.

This release includes the PostgreSQL graph storage updates (#2531),
knowledge memory and recall changes (#2479, #2436), and fixes for
PolarDB recall (#2551), RabbitMQ shutdown (#2532), API key validation
(#2491), and rate limiting (#2490).

## How Has This Been Tested?

- [x] Unit tests — 24 passed in
`tests/graph_dbs/test_postgres_400_compat.py` and
`tests/mem_scheduler/test_rabbitmq_shutdown.py`.
- [x] Verified that both version fields are `2.0.36`, ran `make format`
and `git diff --check`, and simulated the merge with `main`.

## Checklist

- [x] Reviewed the release diff and the two-file version commit.
- [x] Verified the release branch merges cleanly with the current `main`
locally.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:api 云服务 / FastAPI / OpenAPI / MCP status:ready Ready for implementation; waiting for assignee or AI dispatch | 可进入实现,等待认领或派发

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants