You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Every time an assignment goes out and the validation fails we have to dig into the logs to find out the issue.
Describe the solution you'd like
If validation fails it would be great if we can quickly see the logs for the failed validation from within the assignments page.
Describe alternatives you've considered
Show it as a tool tip on the validating link on the assignments page or add a link to the logs and display them on a separate page.
Additional context
This might require we refactor the logging of the validation and store individual validation logs for each assignment on the DB
The text was updated successfully, but these errors were encountered:
I'd rather we don't store logs in the database, let's look at doing what COPR does and just expose them via HTTPS on the filesystem in some place like /opt/quads/log/<assignment_id>/
If we're not storing log logs and maybe just a section of the last failed VE then database makes sense.
sadsfae
changed the title
[FEAT] Add validation logs to web-ui when validation fails
[RFE] Add validation logs to web-ui when validation fails
Mar 25, 2025
Is your feature request related to a problem? Please describe.
Every time an assignment goes out and the validation fails we have to dig into the logs to find out the issue.
Describe the solution you'd like
If validation fails it would be great if we can quickly see the logs for the failed validation from within the assignments page.
Describe alternatives you've considered
Show it as a tool tip on the validating link on the assignments page or add a link to the logs and display them on a separate page.
Additional context
This might require we refactor the logging of the validation and store individual validation logs for each assignment on the DB
The text was updated successfully, but these errors were encountered: