-
-
Notifications
You must be signed in to change notification settings - Fork 154
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
[Error] Can't run linter goanalysis_metalinter: buildir #448
Comments
Same issue. Action Log. |
the cause was found by his comment :) |
getting this issue as well both locally and in ci workflow
|
In theory this can be tied with this: golangci/golangci-lint#827 specifically with this comment: |
I also faced this issue with this workflow. This is a basic workflow to help you get started with Actionsname: Linting and Static Code Analysis on: [push, pull_request] jobs:
Later I updated the golangci-lint version to v1.46.2 (latest one) And it worked. I guess this issue can be resolved. |
i believe in your case go-webp is dependent on some third party binary that is not by default installed on local machine nor the gb action runner. As their github page states: (https://github.com/kolesa-team/go-webp) Requirements - libwebp You have to add preliminary step in you action that will install this dependency before running lint. Go needs to be able to compile your code and it needs all dependencies to do so. |
my golangci-lint version was 1.50.1 not effect |
I got this problem and the issue was a compiler error in one of my vendored dependencies. Once I updated them to fix the error, this error disappeared. |
Ive just noticed this happening to me both on ci and locally.
|
Fwiw, in my case, the same issue was caused by depending on a private repository and solved by following the steps here: |
I have this problem with an external package,
|
I have the same problem with go-pdfium package golang-ci version is 1.52.2
|
Same in 1.54.2.
|
All errors related to Why do you have
|
This comment was marked as off-topic.
This comment was marked as off-topic.
Upgrading the
|
so, my problem was solved when i installed .so files |
For me it was malformed go dependencies made it tidy: |
deleted |
I appreciate your comment here, this is the same problem I had. Thanks! |
Came here to say that this solved a similar problem for me |
This way works for me, thanks. |
I found error suddenly due to go1.18 issue
Then I tried to change configuration followed by the above issue, another error as title happened after configuration changed.
Errors are
configuration
difference from most of common use is I'm using monorepo and I use
working-directory
. I'm not sure.golangcli.yaml
stored in root directory is used properly in this version, thought it used to be work.The text was updated successfully, but these errors were encountered: