Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EmbeddingExtractor Error on put message vectors #45

Closed
rsharath opened this issue May 15, 2023 · 2 comments
Closed

EmbeddingExtractor Error on put message vectors #45

rsharath opened this issue May 15, 2023 · 2 comments
Assignees

Comments

@rsharath
Copy link
Contributor

Zep server throws: Duplicate Key Value error on message_embedding_uuid_key. Should we consider returning a Response Body in the 200 OK to provide some additional error information back to the Client SDKs? Or alternatively consider a different Response Code?

zep | time="2023-05-15T20:38:16Z" level=error msg="EmbeddingExtractor extract failed: extractor error: EmbeddingExtractor put message vectors failed (original error: storage error: failed to put embeddings (original error: storage error: failed to insert message vectors (original error: ERROR: duplicate key value violates unique constraint "message_embedding_message_uuid_key" (SQLSTATE=23505))))"

eted_at": ERROR: duplicate key value violates unique constraint "message_embedding_message_uuid_key" (SQLSTATE=23505)"
zep | time="2023-05-15T20:38:17Z" level=error msg="EmbeddingExtractor extract failed: extractor error: EmbeddingExtractor put message vectors failed (original error: storage error: failed to put embeddings (original error: storage error: failed to insert message vectors (original error: ERROR: duplicate key value violates unique constraint "message_embedding_message_uuid_key" (SQLSTATE=23505))))"

@danielchalef
Copy link
Member

I've merged a fix to main. Would you please confirm that this is fixed?

@danielchalef
Copy link
Member

Confirmed fixed by #47

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

No branches or pull requests

2 participants