-
Notifications
You must be signed in to change notification settings - Fork 2.6k
fix: Application The reference segmentation of the knowledge base retrieval node in the loop body is displayed as 0 #4466
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a few optimizations and improvements that can be made to enhance the code's performance and readability:
Avoid Reversing Loop Order: In
get_loop_workflow_node, reversing the loops (outer for->inner for) is unnecessary. This should not affect the output but might make it harder to understand.Use Set instead of List for Result Accumulation: If you expect duplicates in
loop_node_data, using a set could reduce memory usage compared to a list, although this doesn't make sense in this specific context where order does matter.Consistent Naming Conventions: Ensure consistent naming conventions throughout the codebase. The use of single underscores (
_) for local variables and class methods might improve readability, especially when working in larger projects.Remove Redundant Code from Serializer Creation:
Optimize Query Construction:
Optimized version of fetching chat records
def list(self, with_valid=True):
qs = (
ChatRecord.objects
.filter(chat_id=self.data.get('chat_id'))
.order_by(order_by)
)
if not with_valid:
qs = qs.exclude(is_valid=False)
return [ChatRecordSerializerModel(rec).data for rec in qs]