Repository navigation
fix: restore vectors when segments are re-enabled via API - #7
Merged
Merged
Conversation
Route enable-only segment updates through the existing async status flow so disabled vectors are rebuilt instead of synchronously updated. Refs langgenius#39988
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
Restore knowledge segment vectors when the Service API receives an enable-only patch for a disabled segment. The shared mutation service now dispatches the existing load-based enable task and preserves the segment's content, QA answer, keywords, and word counts. Requests that also edit content or keywords retain their synchronous update behavior.
This is the fork counterpart of langgenius#43865 and addresses langgenius#39988.
Validation
mainat09ae6dc936.make lintandmake type-checkpassed.From Codex