fix(pipecat): handle missing profile in memory retrieval#1033
Open
cat0825 wants to merge 1 commit into
Open
Conversation
Author
|
Author follow-up: current branch is ready for review. The Pipecat memory retrieval path now treats a missing profile as empty static/dynamic memories while preserving existing search result handling, with a regression test for the no-profile API response. |
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
2 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.
Summary
Fixes a crash in
SupermemoryPipecatService._retrieve_memories()when the Supermemory API returnsprofile=Nonefor users with no stored memories.Closes #1027.
What changed
Validation
python -m pytest tests/test_service.py