-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
fix: Workflow cannot respond to errors #1899
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 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 issues and optimizations to suggest in the provided code:
Issues:
Thread Lock: The
threading.Lock
is not used consistently throughout the class. It's better placed at places where critical sections of code need locking, but here it seems unnecessary since there aren't any multi-threaded operations being performed.Return Statements: There are multiple instances where lists are returned instead of single values (
[]
andNone
). This might lead to unexpected behavior when calling functions that expect only one value.Unnecessary Exception Logging: The exception print statement (
traceback.print_exc()
) should be wrapped within try-except blocks to prevent the program from crashing if an exception occurs.Error Handling in Event Nodes: When processing event nodes, there's some error handling in place, but it doesn't seem comprehensive. The response handling can be improved to provide more meaningful information back to the caller.
Node Management: Some methods like
append_node
,base_to_response
,get_write_error_context
have no implementation, which could cause runtime errors if called without further refinement.Optimization Suggestions:
Consistent Return Values: Ensure consistent return values. Instead of returning different types (e.g., list, None), decide on a clear structure for all return values.
Handle Exceptions Properly: Wrap exception logging in try-except blocks to avoid crashing the entire pipeline.
Implement Missing Methods: Fill in the implementations for missing methods such as
append_node
,base_to_response
, andget_write_error_context
.Here's an updated version with these considerations incorporated:
This version removes the unused lock and improves exception handling by using try-except blocks. It also provides basic placeholders for the missing methods, ensuring they will behave predictably once implemented.