Skip to content

Conversation

@glin93
Copy link
Contributor

@glin93 glin93 commented Dec 8, 2025

Description

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 (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 的人

glin1993@outlook.com added 4 commits December 8, 2025 15:42
Recent changes to rebuild_from_source removed original_part, causing file_id to be lost during memory transfer. This resulted in null source_doc_id in logs. This fix restores file_id by falling back to the info dictionary.
In _process_transfer_multi_modal_data, file_ids were not explicitly passed from raw_node.metadata to the info dictionary. This prevented file_content_parser from accessing the file_ids during memory transfer, leading to null source_doc_id in logs. This commit ensures file_ids are properly propagated.
1. file_content_parser: Persist file_id in SourceMessage and restore it in rebuild_from_source to prevent data loss during object reconstruction.
2. multi_modal_struct: Fix indentation and ensure file_ids are propagated via info dict as a safety fallback.
@glin93 glin93 requested a review from CaralHsi December 8, 2025 08:12
@glin93 glin93 closed this Dec 9, 2025
@glin93 glin93 deleted the fix/restore-file-id-in-parser branch December 18, 2025 06:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants