Better Error Reporting for Failed Async Checkers #92

New issue

Open

opened 2025-09-27 17:11:00 +00:00 by hz · 0 comments

hz commented

2025-09-27 17:11:00 +00:00

Owner

We should try to make errors in async submissions more debuggable. Right now if things break, we just get a message about an "unknown error," which is impossible to work with.

Maybe we can dump some info into /tmp or the logs or something, and show a reference number that server admins can use to find some relevant info about what went wrong.

We should try to make errors in async submissions more debuggable. Right now if things break, we just get a message about an "unknown error," which is impossible to work with. Maybe we can dump some info into `/tmp` or the logs or something, and show a reference number that server admins can use to find some relevant info about what went wrong.

hz added the

ui/ux

error reporting

labels

2025-09-27 17:11:00 +00:00

hz added this to the v20.0.0 milestone

2025-11-02 22:09:11 +00:00

No milestone

No assignees

1 participant

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

catsoop/catsoop#92

No description provided.

Rows
Columns