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.

Sign up for GitHub

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

Jump to bottom

Fix formatting of errors in issue repository #1865

Closed
2 tasks
nforro opened this issue Jan 26, 2023 · 0 comments · Fixed by #2544
Closed
2 tasks

Fix formatting of errors in issue repository #1865

nforro opened this issue Jan 26, 2023 · 0 comments · Fixed by #2544
Labels
area/fedora Related to Fedora ecosystem area/user-experience Usability issue complexity/easy-fix No planning/thinking about design needed, should be finished in an hour. 🌞 friday 🤟 Weekend is coming! gain/low This doesn't bring that much value to users. good-first-issue Good for newcomers. impact/high This issue impacts multiple/lot of users. kind/bug Something isn't working.

Comments

@nforro
Copy link
Member

nforro commented Jan 26, 2023

This is an example of a reported Bodhi update failure (from packit/specfile#194):

dist-git branch error
epel9 ``` There is a problem with creating a bodhi update:
{"status": "error", "errors": [{"location": "body", "name": "builds", "description": "Cannot find any tags associated with build: python-specfile-0.13.1-1.el9"}, {"location": "body", "name": "builds", "description": "Cannot find release associated with build: python-specfile-0.13.1-1.el9, tags: []"}]} ```

Tasks:

  • Make sure there are no newlines that would break formatting
  • Extract only error description from the exception
@lbarcziova lbarcziova added good-first-issue Good for newcomers. 🌞 friday 🤟 Weekend is coming! labels Jan 26, 2023
@lachmanfrantisek lachmanfrantisek added kind/bug Something isn't working. area/user-experience Usability issue area/fedora Related to Fedora ecosystem complexity/easy-fix No planning/thinking about design needed, should be finished in an hour. impact/high This issue impacts multiple/lot of users. gain/low This doesn't bring that much value to users. labels Jan 8, 2024
kapr200 added a commit to kapr200/packit-service that referenced this issue Sep 24, 2024
@kapr200
Switch to HTML table for downstream error reporting
6d19582 
Fixes packit#1865
@kapr200 kapr200 mentioned this issue Sep 24, 2024
Merged
4 tasks
kapr200 added a commit to kapr200/packit-service that referenced this issue Sep 25, 2024
@kapr200
Switch to HTML table for downstream error reporting
83cb0b5 
Fixes packit#1865
softwarefactory-project-zuul bot added a commit that referenced this issue Oct 1, 2024
@softwarefactory-project-zuul
Switch to HTML table for downstream error reporting (#2544)
5b5e430 
Switch to HTML table for downstream error reporting

Fixes #1865

TODO:

 Write new tests or update the old ones to cover new functionality.
 Update doc-strings where appropriate.
 Update or write new documentation in packit/packit.dev.
 ‹fill in›



Fixes
Related to
Merge before/after

RELEASE NOTES BEGIN
The downstream error reporting, had been switched to html.
RELEASE NOTES END

Reviewed-by: Matej Focko
Reviewed-by: Laura Barcziová
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/fedora Related to Fedora ecosystem area/user-experience Usability issue complexity/easy-fix No planning/thinking about design needed, should be finished in an hour. 🌞 friday 🤟 Weekend is coming! gain/low This doesn't bring that much value to users. good-first-issue Good for newcomers. impact/high This issue impacts multiple/lot of users. kind/bug Something isn't working.
Projects
Packit Kanban Board
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Switch to HTML table for downstream error reporting kapr200/packit-service
3 participants
@nforro @lachmanfrantisek @lbarcziova