Improve error handling #1
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
shy/Parcell#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently (as of
1396cecda1), when an error occurs during request handling, the system returns a generic error code without additional context.There is no further information attached to the response, and no messages are logged to the console, which makes troubleshooting difficult and makes usage of the HTTP API more complex.
Therefore, it is a good idea to add log messages when errors occur and to add more error information in failed HTTP responses.
This issue is to track the development progress thereof.