Skip to content
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

Merged
merged 17 commits into from Jul 15, 2020

Conversation

rbreeze
Copy link
Member

@rbreeze rbreeze commented Jul 13, 2020

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
  • The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
  • I've signed the CLA.
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My builds are green. Try syncing with master if they are not.
  • My organization is added to USERS.md.

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
Copy link
Contributor

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

Copy link
Member

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Member

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

Copy link
Member

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"

Copy link
Member

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
Copy link
Member

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
Copy link
Member

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"

pkg/apis/workflow/v1alpha1/workflow_types.go Outdated Show resolved Hide resolved
pkg/apis/workflow/v1alpha1/workflow_types.go Outdated Show resolved Hide resolved
pkg/apis/workflow/v1alpha1/workflow_types.go Outdated Show resolved Hide resolved
pkg/apis/workflow/v1alpha1/workflow_types.go Outdated Show resolved Hide resolved
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
Copy link
Member

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
Copy link
Member

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

@rbreeze rbreeze merged commit 7a8e2b3 into argoproj:master Jul 15, 2020
@rbreeze rbreeze deleted the nodephase-docs branch August 8, 2020 00:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants