mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
Do not ignore errors ever #1205
Labels
No labels
I1
I2
I3
I4
S0
S1
S2
S3
S4
U0
U1
U2
U3
U4
blocked
bug
config
dependencies
discussion
documentation
enhancement
enhancement
epic
feature
go
good first issue
help wanted
neofs-adm
neofs-cli
neofs-cli
neofs-cli
neofs-ir
neofs-lens
neofs-storage
neofs-storage
performance
question
security
task
test
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-node#1205
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?
Originally created by @carpawell on GitHub (Apr 2, 2024).
Expected Behavior
Never ignore errors in gonang.
Current Behavior
Code may ignore some errors (even if they are not expected at all, that is not good).
Possible Solution
Panic if an error is not expected at all.
Context
At least CLIs are affected: binding flags, getting flags, marking flags.
Some other places may be affected too.
@roman-khimov commented on GitHub (Apr 2, 2024):
Narrow down the scope, please. This is too broad.
@carpawell commented on GitHub (Apr 2, 2024):
Finding all the places == 90% of solving the issue. We do ignore errors sometimes (
Contexthas 3 examples withcobralib errs ignorance). What exact do you mean?