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
docs: Add comments to NodePhase definition. Closes #1117. #3467
Conversation
NodeFailed NodePhase = "Failed" // a WF with a failed Node will be marked with NodeFailed as well | ||
// There was an error within the container. E.g. the container exits with a non 0 code | ||
NodeError NodePhase = "Error" // a WF with an errored Node will be marked with NodeError as well | ||
// There was an error around a container, E.g. The pod was deleted, couldn’t be scheduled, or there were problems getting logs |
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.
I don't think this is correct - @simster7
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.
Seems correct to me. What do you think is wrong @alexec?
NodeFailed NodePhase = "Failed" | ||
NodeError NodePhase = "Error" | ||
NodeOmitted NodePhase = "Omitted" | ||
NodePending NodePhase = "Pending" // WF/Node is waiting to run |
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.
NodePending NodePhase = "Pending" // WF/Node is waiting to run | |
NodePending NodePhase = "Pending" // Node is waiting to run |
This is cleaner
NodeSucceeded NodePhase = "Succeeded" // WF/Node has finished with no errors | ||
NodeSkipped NodePhase = "Skipped" // Node was skipped in Workflow DAG / Steps | ||
NodeFailed NodePhase = "Failed" // a WF with a failed Node will be marked with NodeFailed as well | ||
// There was an error within the container. E.g. the container exits with a non 0 code |
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.
It's not standard to put a docstring below its definition. If it doesn't fit on the same line then all of the docstrings for this type should be above their definitions
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.
I would simply say "Node or child of node exited with non-0 code"
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.
I would simply say "Node or child of node exited with non-0 code"
This doesn't look addressed
NodeSucceeded NodePhase = "Succeeded" // WF/Node has finished with no errors | ||
NodeSkipped NodePhase = "Skipped" // Node was skipped in Workflow DAG / Steps | ||
NodeFailed NodePhase = "Failed" // a WF with a failed Node will be marked with NodeFailed as well | ||
// There was an error within the container. E.g. the container exits with a non 0 code |
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.
I would simply say "Node or child of node exited with non-0 code"
// There was an error within the container. E.g. the container exits with a non 0 code | ||
// a WF with a failed Node will be marked with NodeFailed as well | ||
NodeFailed NodePhase = "Failed" | ||
// There was an error around a container, E.g. The pod was deleted, couldn’t be scheduled, or there were problems getting logs |
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.
I would simply say "Node had an error other than a non-0 exit code"
Co-authored-by: Simon Behar <simbeh7@gmail.com>
Co-authored-by: Simon Behar <simbeh7@gmail.com>
Co-authored-by: Simon Behar <simbeh7@gmail.com>
Co-authored-by: Simon Behar <simbeh7@gmail.com>
NodeSucceeded NodePhase = "Succeeded" // WF/Node has finished with no errors | ||
NodeSkipped NodePhase = "Skipped" // Node was skipped in Workflow DAG / Steps | ||
NodeFailed NodePhase = "Failed" // a WF with a failed Node will be marked with NodeFailed as well | ||
// There was an error within the container. E.g. the container exits with a non 0 code |
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.
I would simply say "Node or child of node exited with non-0 code"
This doesn't look addressed
// There was an error within the container. E.g. the container exits with a non 0 code | ||
// a WF with a failed Node will be marked with NodeFailed as well | ||
NodeFailed NodePhase = "Failed" | ||
// Node had an error other than a non 0 exit code. E.g. The pod was deleted, couldn’t be scheduled, or there were problems getting logs |
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.
I would simply say "Node had an error other than a non-0 exit code"
This doesn't look addressed
Checklist:
"fix(controller): Updates such and such. Fixes #1234"
.