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

A little less verbose error reporting #2535

Open
1 of 2 tasks
praiskup opened this issue Sep 19, 2024 · 2 comments
Open
1 of 2 tasks

A little less verbose error reporting #2535

praiskup opened this issue Sep 19, 2024 · 2 comments
Labels
area/general Related to whole service, not a specific part/integration. area/user-experience Usability issue complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/low This issue impacts only a few users. kind/feature New feature or a request for enhancement.

Comments

@praiskup
Copy link

Description

It would be nice to make the comment from Packit service smaller - the thing is that it never disappears, even if the original problem disappears. The issue/PR stays forever with a large comment like this:
Screenshot_20240919_155828

I'm not proposing any solution, just a few examples:

  • make the text a one-liner -> pointing at a different page that user may observe
  • hide the text once the problem disappears
  • modify the comment if the problem disappears (that's how pep2speaks behaves)
  • do not issue the comment at all, just create the failed task list

Lemme admit that I know this example error is actually a Copr fault. WIP. But the particular PR have re-run Packit builds/tests and these are all finished and "green" already.

Benefit

No response

Importance

Low, but shorter messages will make the UI nicer.

What is the impacted category (job)?

General

Workaround

  • There is an existing workaround that can be used until this feature is implemented.

Participation

  • I am willing to submit a pull request for this issue. (Packit team is happy to help!)
@praiskup praiskup added the kind/feature New feature or a request for enhancement. label Sep 19, 2024
@lbarcziova lbarcziova added the discuss discuss To be discussed within a team (usually on the so-called Architecture meeting next Thursday) label Sep 24, 2024
@praiskup
Copy link
Author

Similar here:
Screenshot_20240924_122055

@lbarcziova
Copy link
Member

Hi! Thanks for creating this. The option of migrating most of the content, e.g., to our docs and just linking in comments sounds the most suitable to us. (The already existing comment modification/hiding could be prone to race conditions.)

@lbarcziova lbarcziova added area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. impact/low This issue impacts only a few users. gain/low This doesn't bring that much value to users. area/user-experience Usability issue and removed discuss discuss To be discussed within a team (usually on the so-called Architecture meeting next Thursday) labels Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/general Related to whole service, not a specific part/integration. area/user-experience Usability issue complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/low This issue impacts only a few users. kind/feature New feature or a request for enhancement.
Projects
Status: backlog
Development

No branches or pull requests

2 participants