Skip to content

[RFE] Add validation logs to web-ui when validation fails #584

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

Open
grafuls opened this issue Mar 24, 2025 · 1 comment
Open

[RFE] Add validation logs to web-ui when validation fails #584

grafuls opened this issue Mar 24, 2025 · 1 comment

Comments

@grafuls
Copy link
Contributor

grafuls commented Mar 24, 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

@sadsfae
Copy link
Member

sadsfae commented Mar 25, 2025

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 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
@sadsfae sadsfae added this to the 2.x Series - Bowie milestone Mar 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To do
Development

No branches or pull requests

2 participants