fix(webui): resolve document status grouping issue in DocumentManager #2013
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
- Move dependency analysis outside graph database lock - Add persistence call before lock release to prevent dirty reads
…scription merging
This ensures the KG rebuilds maintain the original creation order of the first extraction result for each chunk.
…ve parameter validation for summary configuration - Update algorithm logic in operate.py for better token management - Fix health endpoint to use correct parameter names
- Modified _handle_entity_relation_summary to return tuple[str, bool] - Updated merge functions to log "LLMmerg" vs "Merging" based on actual LLM usage - Replaced hardcoded fragment count prediction with real-time LLM usage tracking
… summary trigger frequency
…mmary - Add SUMMARY_LENGTH_RECOMMENDED parameter (600 tokens) - Optimize prompt temple for LLM summary
- Remove hash delimiters - Consistent section headers - Add "Output:" labels - Clean up example formatting
- Remove parameter from function signature - Access from global_config instead - Improve code consistency
- Ensure oversized descriptions are force-merged with subsequent ones - Add len(current_list) <= 2 termination condition to guarantee convergence - Implement token-based truncation in _summarize_descriptions to prevent overflow
- Fix documents being grouped by status after pagination and sorting - Use backend-sorted data directly from currentPageDocs instead of re-grouping - Preserve backend sort order to prevent status-based grouping - Maintain backward compatibility with legacy docs structure - Ensure all sorting fields (file name, dates, ID) work correctly without status grouping The issue occurred because the frontend was re-grouping already-sorted data from the backend by status, breaking the intended sort order. Now documents are displayed in the exact order returned by the backend API. Fixes: Document list sorting by file name was grouping by status instead of maintaining proper sort order across all documents.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
fix(webui): resolve document status grouping issue in DocumentManager
The issue occurred because the frontend was re-grouping already-sorted data
from the backend by status, breaking the intended sort order. Now documents
are displayed in the exact order returned by the backend API.
Fixes: Document list sorting by file name was grouping by status instead of
maintaining proper sort order across all documents.