-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
chore: fix a bunch of issues caught by golangci-lint #6140
Conversation
core/coreunix/add.go
Outdated
if err == nil { | ||
err = adder.bufferedDS.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.
Cause of #6139 (comment). We're ignoring the add error for small files.
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 will need a named err
return value or something. Right now it references the first declared err
and doesn't intercept any of the ones down below.
I got an unrelated error that looks like a leveldb bug.
|
Codeclimate has one more new issue for you. |
5f12c58
to
dbd7185
Compare
see: #6140 (comment) License: MIT Signed-off-by: Steven Allen <[email protected]>
Most of these are probably harmless but a few looked like they might actually be bugs. Most of them are just faulty tests. License: MIT Signed-off-by: Steven Allen <[email protected]>
License: MIT Signed-off-by: Steven Allen <[email protected]>
1. Yes, I like my symmetry. 2. No, we don't want to stash the private key if we fail to put it in the peerstore. License: MIT Signed-off-by: Steven Allen <[email protected]>
8eb7321
to
5ee455b
Compare
I've moved the add fix to #6156 so we can merge it sooner. |
@Kubuxu can I get a signoff? |
chore: fix a bunch of issues caught by golangci-lint This commit was moved from ipfs/kubo@fd15c62
Most of these are probably harmless but a few looked like they might actually be bugs. Most of them are just faulty tests.
Why? Well, I thought "let me just try running this linter..." and then spent way more time than I should have on this.