-
Notifications
You must be signed in to change notification settings - Fork 2.6k
fix: Judgment execution logic #4072
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
+12
−4
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.
The provided code seems to be part of a method that checks whether a given node has any dependencies from its upstream nodes, particularly those within an ongoing flow or process. There are a few potential issues and improvements:
Use of Static Method: The
dependent_nodemethod is currently implemented as static but accesses non-static attributes (edge.sourceNodeId). This might lead to unexpected behavior if used incorrectly.Variable Naming Convention: While consistent with Python variable naming conventions (using lowercase letters separated by underscores), there could still be minor inconsistencies in variable names like
up_edge_list.Redundant List Comprehension: In the
get_next_nodemethod, you have multiple lines similar to each other but perform almost identical operations on lists. Reducing redundancy can improve readability and efficiency.Edge Validation: Ensure that every edge source or target node exists in the
self.node_contextdictionary. Missing or extraneous edges might cause errors later in the function or during execution.Context Handling: The context handling for different types of nodes (e.g., 'form-node') assumes specific key values ('branch_id' and 'form_data'). Consider adding error checks or logging when these keys aren't present to handle exceptions gracefully.
Here's a revised version with some suggested optimizations and corrections:
In this revision:
dependent_nodeto ensure it receives a valid edge object.lambda.is_dependentandfiltered_up_edges, keeping the logic straightforward.This should address most of the issues mentioned while maintaining functionality.