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

frontend: provide log-detective explain integration for failed builds #3608

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

nikromen
Copy link
Member

@nikromen nikromen commented Jan 28, 2025

@nikromen nikromen force-pushed the log-detective-integration branch from d51316c to b9793b7 Compare January 28, 2025 15:51
<a href="{{ failed_build_log_url | format(url) }}" class="btn btn-default btn-xs">
<span class="pficon pficon-info"></span> Explain with Log Detective AI
</a>
{% endif %}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we place this into a separate column, since this is not a log file but "request for explanation".

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or, maybe we could have a clickable "failed" state? Can you upload a screenshot?

@@ -157,6 +157,12 @@
<span class="pficon pficon-ok"></span> {{ state }}
{% elif state == "failed" %}
<span class="pficon pficon-error-circle-o"></span> {{ state }}
{% if failed_build_log_url and config.LOG_DETECTIVE_BUTTON %}
Copy link
Member

@praiskup praiskup Jan 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The used config option is ON in prod, and we want to keep this new UI disabled for some time... I think we need yet another option.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe not, it will be quite some time before we'll do a new Copr release anyway.


Returns:
the full URL to the log file or None if the log file does not exist
"""
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤷 this rewrite is weird, can we have a separate method for the new link?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or IMHO even better, can we improve log detective to handle the compressed logs?

@praiskup
Copy link
Member

praiskup commented Feb 7, 2025

Would you mind uploading the screenshot?

@nikromen nikromen force-pushed the log-detective-integration branch from b9793b7 to 42a89fa Compare February 8, 2025 23:38
@nikromen nikromen changed the title feat: provide log-detective explain integration for failed builds frontend: provide log-detective explain integration for failed builds Feb 8, 2025
@nikromen
Copy link
Member Author

nikromen commented Feb 8, 2025

button next to the fail state:

srpm failure
srpm

rpm failure
rpm

or 793ee5b introduces separate column for the table

separated column when rpm build fails
sloupecek2

no separated column created when srpm fails
srpm_no_sloupecek

@nikromen nikromen force-pushed the log-detective-integration branch from 42a89fa to 793ee5b Compare February 8, 2025 23:50
@nikromen nikromen force-pushed the log-detective-integration branch from 793ee5b to e079ab3 Compare February 9, 2025 00:00
@FrostyX
Copy link
Member

FrostyX commented Feb 9, 2025

IMHO the buttons come out too aggressive. I would probably go with a normal link and an icon (to look the same as the chroot name in the first column). And I would probably shorten the text to something like "Explain failure" or "Explain with AI".

@nikromen
Copy link
Member Author

like this?

kubas-feedback

@praiskup
Copy link
Member

praiskup commented Feb 10, 2025

From the meeting: [x] failed (Ask AI / Teach AI)

Copy link

Pull Request validation

Failed

🔴 Review - Missing review from a member (2 required)

Success

🟢 CI - All checks have passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants