Don't ignore errors completely #328
Labels
No Label
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#328
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Is your feature request related to a problem? Please describe.
There are several places: 1, 2, 3 and some others where we ignore errors completely. It will be hard to known what went wrong without proper error handling.
Describe the solution you'd like
We should at least log errors in such cases.
Describe alternatives you've considered
Handle error and fail request
Additional context
Places without error handling were found by Svace