fix: replace .single() with .maybeSingle() in SupabaseDB.get() to handle missing rows#4599
Merged
whysosaket merged 1 commit intomem0ai:mainfrom Apr 1, 2026
Conversation
kartik-mem0
approved these changes
Apr 1, 2026
whysosaket
approved these changes
Apr 1, 2026
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
3 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.
Fixes #4596
Problem
SupabaseDB.get(vectorId)used.single()which throwsPGRST116when no row exists. A missing row is not an error — it's a valid not-found case.Fix
Replace
.single()with.maybeSingle()on line 270 ofsupabase.ts. This returnsnullinstead of throwing when no row is found, which is already handled correctly by theif (!data) return nullcheck.