fix(memory): normalize non-canonical extraction payloads#1416
Open
yeyitech wants to merge 2 commits intovolcengine:mainfrom
Open
fix(memory): normalize non-canonical extraction payloads#1416yeyitech wants to merge 2 commits intovolcengine:mainfrom
yeyitech wants to merge 2 commits intovolcengine:mainfrom
Conversation
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨No code suggestions found for the PR. |
Contributor
Author
|
Updated based on the review suggestions. I restored lightweight observability for normalized non-canonical extraction payloads and added regression coverage for the new logging paths. |
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.
Summary
{"memories": [...]}formNoneWhy
Closes #1410.
Some smaller local / OpenAI-compatible models appear to return payloads that are structurally close to the expected schema but not exact, for example:
{"memories": {...}}instead of{"memories": [{...}]}itemsor nesteddata.memoriesBefore this change those responses could normalize to an empty result, causing
memories_extractedto stay empty even when the model had clearly understood the conversation.Validation
python3 -m py_compile openviking/session/memory_extractor.py tests/session/test_memory_extractor_response_types.pypython3 -m pytest -o addopts='' -p no:asyncio --noconftest tests/session/test_memory_extractor_response_types.py tests/session/test_memory_extractor_language.py -q