-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blobstor: Additional context of errors #2608
Conversation
4b946de
to
b285958
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #2608 +/- ##
==========================================
- Coverage 28.67% 28.67% -0.01%
==========================================
Files 415 415
Lines 32234 32253 +19
==========================================
+ Hits 9244 9249 +5
- Misses 22195 22207 +12
- Partials 795 797 +2 ☔ View full report in Codecov by Sentry. |
977868e
to
9e833e3
Compare
9e833e3
to
f8eeef6
Compare
@@ -46,7 +46,7 @@ func (t *FSTree) writeData(p string, data []byte) error { | |||
} | |||
|
|||
// unreachable, but precaution never hurts, especially 1 day before release. | |||
return fmt.Errorf("couldn't read file after %d retries", retryCount) | |||
return fmt.Errorf("couldn't write file after %d retries", retryCount) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wow, more like a bugfix for a separate commit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is not a bug, just typo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
logging "read" while writing is a bug to me. do not insist on a separate commit much
Conflicts. |
Do we still need this? |
It has some little fixes. But should be rebased first to unserstand if it is good still. |
f8eeef6
to
80358f1
Compare
Some errors may be too generic to detect the exact place they come from. Additional context helps. Signed-off-by: Leonard Lyubich <[email protected]>
After Go introduced `fs` package, error checkers from `os` packages may be replaced with more laconic `errors.Is` ones. An additional benefit is support for wrapped errors, which was not present in the old functions. Signed-off-by: Leonard Lyubich <[email protected]>
Type helps to realize what exact storage failed. Signed-off-by: Leonard Lyubich <[email protected]>
Previously, object command that opened dynamic session with storage node (like `put`) failed with `can't fetch current epoch: can't parse RPC endpoint: missing port in address` error when RPC endpoint was set in the config file and omitted in flags. Get network endpoint from viper box which contains values from config file. Refs #1574. Signed-off-by: Leonard Lyubich <[email protected]>
80358f1
to
2ad8cfd
Compare
rebased |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It becomes too chatty to me, but OK (there are some nices fixes there as well).
@roman-khimov my goal is to avoid messagges like in the PR body when i can only imagine what the exact problem is at the same time, i dont wanna force such changes cuz of usefule fixes only, so i can split fixes (we'll merge them now) and error context changes (can hang for now) |
Hanging changes are no good, they're either in or out. |
Originally posted by @smallhive