Repository navigation
Fix customer chat deletion races and make RAG latency profiling safe - #18
Merged
Merged
Conversation
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
This PR addresses the two customer-demo issues reported in the live Servy RAG UI.
1. Prevent deleted chats from reappearing
2. Make latency profiling measurable and non-polluting
Tests and CI
.github/workflows/ci.yml.Safety
No production database, approved manuals, embeddings, Chroma collections, access codes or existing conversation records were changed by these edits. The profiler soft-deletes only UUIDs it created itself.
Local validation still required
The profiler has not been run against the local
servy_devgateway from this GitHub-only change. After CI passes, run it locally using the existing private access-file path; do not share the access code.