Proper error logging #16

Open
opened 2024-07-15 08:30:48 +02:00 by Jef Roosens · 0 comments

A lot of actions can produce errors, e.g. parsing packages, generating package archives etc.

All of these errors should be handled properly, with actions being retried as needed depending on what kind of error occured. The errors should also be logged in the database to allow an admin user to inspect them. This will be especially useful once I start work on the web ui, where an admin interface can provide access to this data.

A lot of actions can produce errors, e.g. parsing packages, generating package archives etc. All of these errors should be handled properly, with actions being retried as needed depending on what kind of error occured. The errors should also be logged in the database to allow an admin user to inspect them. This will be especially useful once I start work on the web ui, where an admin interface can provide access to this data.
Jef Roosens added the
enhancement
label 2024-07-15 08:30:48 +02:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Chewing_Bever/rieter#16
There is no content yet.