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.
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
Pass an error message to the failure node #6181
Pass an error message to the failure node #6181
Changes from 6 commits
bde2f15
94dde9a
ca98e5b
ab9dfd2
4414f89
3ed4177
d5e5b6f
bdafc54
a9d3e3a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Consider adding assertions to verify that the
execErr
is correctly set in theFailureNodeLookup
struct. Currently, the test doesn't validate theOriginalError
field.Code suggestion
Code Review Run #4749b8
Is this a valid issue, or was it incorrectly flagged by the Agent?
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.
could we add an assert below
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.
Consider adding a test case to verify behavior when
originalErr
isnil
. The type assertion toFailureNodeLookup
assumes the cast will always succeed.Code suggestion
Code Review Run #f10373
Is this a valid issue, or was it incorrectly flagged by the Agent?
Check warning on line 776 in flytepropeller/pkg/controller/nodes/executor.go
flytepropeller/pkg/controller/nodes/executor.go#L771-L776
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.
Consider adding error handling for the case when
execErr
is nil. Currently, the function assumesexecErr
is non-nil when accessingGetMessage()
.Code suggestion
Code Review Run #4749b8
Is this a valid issue, or was it incorrectly flagged by the Agent?
Check warning on line 172 in flytepropeller/pkg/controller/nodes/subworkflow/subworkflow.go
flytepropeller/pkg/controller/nodes/subworkflow/subworkflow.go#L172
Check warning on line 15 in flytepropeller/pkg/utils/assert/literals.go
flytepropeller/pkg/utils/assert/literals.go#L14-L15
Check warning on line 21 in flytepropeller/pkg/utils/assert/literals.go
flytepropeller/pkg/utils/assert/literals.go#L20-L21
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.
if one of the structure is nil, we should also raise an error
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.
Consider adding a test case to verify behavior when one structure is nil and the other is not. Currently, the code only checks when both are nil or both are non-nil.
Code suggestion
Code Review Run #f0fe6a
Is this a valid issue, or was it incorrectly flagged by the Agent?
Check warning on line 51 in flytepropeller/pkg/utils/assert/literals.go
flytepropeller/pkg/utils/assert/literals.go#L50-L51
Check warning on line 59 in flytepropeller/pkg/utils/assert/literals.go
flytepropeller/pkg/utils/assert/literals.go#L58-L59