-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
golangci-lint shows "killed" immediately #5042
Comments
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
I did try to run the code directly and it gave me a response.
but then running the executable gave the same "killed" error again |
Hello, The process can be killed for different reasons:
But in your case, you must use at least go1.22 to compile golangci-lint. There is no need for explicit GOOS/ARCH unless you are compiling for another system than yours. Also, I recommend using our binaries instead of compiling ( |
ended up using this to solve the issue: https://stackoverflow.com/questions/51833310/what-is-killed9-and-how-to-fix-in-macos-terminal
|
This is also happening to me. It started two weeks ago. It hasn't happened yet for any of my colleagues. macOS 14.7 The process is killed because of an invalid code signature. This is the only go binary where I've observed this problem.
Like the original poster, resigning worked for me.
|
Based on issues on Go: https://github.com/golang/go/issues?q=is%3Aissue+%22Code+Signature+Invalid%22+is%3Aclosed The problem seems to be related to tooling inside MacOS. |
Welcome
typecheck
section of the FAQ.Description of the problem
when I try to run any command for "golangci-lint"
like:
it shows:
Version of golangci-lint
I cant dump the full content, I just know its the version.
Configuration
# paste configuration file or CLI flags here
Go environment
Verbose output of running
A minimal reproducible example or link to a public repository
Validation
Supporter
The text was updated successfully, but these errors were encountered: