fix: Folder Sync Improvements - Source Path Tracking & LightRAG Fallback #138
+395
−10
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 fixes folder sync functionality with two key improvements:
1. Fixed New File Detection (Source Path Tracking)
Problem: Files always appeared as "new" after sync because:
detect_folder_changeschecks source paths (in linked folder)synced_filesstored destination paths (in KB raw directory)Solution: Now stores source paths in
synced_files, matching whatdetect_folder_changesexpects.2. LightRAG Fallback for RAGAnything
Problem: When RAGAnything module was unavailable, sync would fail with
ImportError.Solution: Gracefully falls back to LightRAG pipeline:
Files Changed
src/api/routers/knowledge.py- Addedfolder_idparam and source path trackingsrc/knowledge/add_documents.py- Added LightRAG fallback methodsTesting