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

Render additional workload information in jobby list #86

Closed
3 tasks done
nicholasjng opened this issue Sep 6, 2024 · 0 comments · Fixed by #89
Closed
3 tasks done

Render additional workload information in jobby list #86

nicholasjng opened this issue Sep 6, 2024 · 0 comments · Fixed by #89
Assignees
Labels
client Related to the client component. enhancement New feature or request

Comments

@nicholasjng
Copy link
Collaborator

nicholasjng commented Sep 6, 2024

In addition to the higher-level status (executing | failed | succeeded), we would like to display some more information that could indicate to the user that something noteworthy happened over the course between submission and execution:

  • Indicate previous pre-emption by other jobs, if they took place (can query this from the status condition list). (done in Add jobby list CLI command #82)
  • Indicate failed pods associated with a workload, since those indicate a fundamental problem with the submitted code/image (optional, since it involves handling every type of workload separately).
  • Indicate if a submitted workload has been inadmissible in the past. (done in Add jobby list CLI command #82)
@nicholasjng nicholasjng added enhancement New feature or request client Related to the client component. labels Sep 6, 2024
@nicholasjng nicholasjng self-assigned this Sep 6, 2024
@AdrianoKF AdrianoKF linked a pull request Sep 6, 2024 that will close this issue
@AdrianoKF AdrianoKF removed a link to a pull request Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client Related to the client component. enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant