Does P/R/C reporting on argo list -o wide still work?

[withnale]

Whenever I try running any of our workflows and I used

argo list -o wide  -A

NAMESPACE   NAME                                                         STATUS      AGE   DURATION   PRIORITY   P/R/C   PARAMETERS
dev         dev-abc-defghij-default-1659528000                           Running     4m    4m         0          0/0/0
dev         stable-another-job-def-g64cn                                 Succeeded   11d   7h         0          0/0/0

I've tried this with our job definitions and I've also tried this out of the box some of the workflows in argo-workflows/examples and I've yet to see a case where it works.

Summary

What happened/what you expected to happen?

The P/R/C column is populated based on the number of pending/running/completed steps of the workflow.

What version are you running?

We're running v3.2.9 but I've also tried it with v3.3.7

[alexec]

This happen because of this line of code:

https://github.com/argoproj/argo-workflows/blob/f27475feb850dc43e07c3c5215cc9638947f0859/cmd/argo/commands/list.go#L48

It should be easy to add an option for wide.

[aditya-shrivastava]

Hi @alexec, I am new to open source and would like to try and work on this issue. Can you assign it to me?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions.

[aditya-shrivastava]

Update on the issue: I have been learning Go and Kubernetes and reviewing the documentation to better understand the project.

[aditya-shrivastava]

Hi @alexec, I have made the following changes:

After running make cli I was able to submit an example workflow to get the expected P/R/C results:

Log of the example workflow:

Kindly let me know if this fixes the issue or if I need to make more changes. Also, I would highly appreciate it if you could tell me what unit tests I should add for the above changes before making a pull request. :smiley: