Get rid of could not
in the beginning of the wrapped error messages #1535
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1535
Loading…
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?
It makes each error unreadable, while adding nothing to the context.
Same for
failed to
, same forcan't
.Basically,
what we did: %w
.https://github.com/uber-go/guide/blob/master/style.md#error-wrapping has more elaborate rationale.
The only way for error to be handled is logging and there we use either field name or level, so this context won't be lost.
The last part would be to find or create a linter which catches the most common verbs.