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

Extend the failed message in the ui. #68

Closed
GarciaSiego opened this issue Feb 3, 2020 · 5 comments · Fixed by #93
Closed

Extend the failed message in the ui. #68

GarciaSiego opened this issue Feb 3, 2020 · 5 comments · Fixed by #93

Comments

@GarciaSiego
Copy link

Currently the Bull-board is not providing the needed info.

For example when a job fails we retry it X amount of times depending on the endpoint and this returns ‘job stalled more than allowable limit’ when it fails. Before in Kueue this would give the data object which contained the reason for failing.

Currently it's only possible to see the complete message by calling ‘jobs/failed/retrieve/0/99999999’ endpoint.

For this I would like the DATA and OPS object to be added to the failed job or an other solution would be to add a link to retrieve the complete message.

Solution one extend the array of queue(ui/components/Queue.js 63) :
failed: ['id', 'failedReason','data', 'timestamps', 'progress', 'attempts', 'retry'],

@O1lpunch3r
Copy link

Yeah, i would be nice to see job-data and job-options in failed tab.

@Juanperezc
Copy link

I think it would be very helpful

@vcapretz
Copy link
Contributor

vcapretz commented Mar 27, 2020

hey, I might do it!

Just want to be clear: 😅
what is needed is that the failed tab also shows the data and opts fields right? so you get access to the job's original data

@O1lpunch3r
Copy link

hey, I might do it!

Just want to be clear: sweat_smile
what is needed is that the failed tab also shows the data and opts fields right? so you get access to the job's original data

Exactly :)

@vcapretz
Copy link
Contributor

done and release in v1.0.0-alpha.6 😄

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 a pull request may close this issue.

4 participants