-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
bodyclose: panic #733
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
Labels
bug
Something isn't working
Comments
Closed
stevenh
added a commit
to stevenh/bodyclose
that referenced
this issue
Sep 24, 2019
Fix a panic caused by using a nil Call.Method. Fixes golangci/golangci-lint#733
I created a fix timakin/bodyclose#22 |
hehe same fix as I did too golangci/bodyclose#1 ;-) |
I chose to create my PR on the upstream, because I still have hope 😄 |
hi, I've merged golangci/bodyclose#1. |
And I've updated bodyclose in the master branch |
korjavin
added a commit
to korjavin/golangci-lint-1
that referenced
this issue
Sep 28, 2019
* tag 'v1.19.1': Use separate go.mod/go.sum to manage tool deps. (golangci#736) Use stretchr/testify to mock log. Fix golangci#733: update forked bodyclose Cleanup obsolete go.mod/go.sum diff. (golangci#729) dev: update deprecated parts of .goreleaser.yml dev: trigger CI build on tag push Update minimum Go version to 1.12. Enable consistent GOPROXY Go 1.12/1.13 behavior. Fix golangci#608: use forked bodyclose Drop memory usage of go/analysis linters 5x Manage build tools via go.mod. Update whitespace Reduce memory usage of go/analysis
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running golangci-lint run with
bodyclose
enable it panicsThe text was updated successfully, but these errors were encountered: