-
Notifications
You must be signed in to change notification settings - Fork 3
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
Stop analysis on 3rd party code #9
Comments
try this command golang-ci long time no release, 😢 |
Thank you, this works. However, contextcheck has no configuration in golangci-lint and we use that. |
'pkgprefix' option is not need in golang-ci, it work for standalone cli only. new version released https://github.com/golangci/golangci-lint/releases/tag/v1.50.0 |
I'm testing golangci-int 1.50.0 with contextcheck and I have the same issue with the very same jwt library. Any advice? |
show me some code |
So I upgraded to 1.50 and only change is, that error format is changed too:
You can verify that with this repository https://github.com/indykite/jarvis-sdk-go |
I think the pkgpath filtering function is invalid.. it's a bug. |
I'm not really sure. Because when I execute this |
I'm sure, because wait next golang-ci release... |
I had to do several things: - contextcheck now supports Go 1.18 generics, but I had to disable it because of this kkHAIKE/contextcheck#9 - dupword produces to many false positives, so it's also disabled - revive found all packages which didn't have a documentation comment before. And tehre is A LOT of them. I updated some of them, but gave up at some point and just added them to exclude rules for now. Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
I had to do several things: - contextcheck now supports Go 1.18 generics, but I had to disable it because of this kkHAIKE/contextcheck#9 - dupword produces to many false positives, so it's also disabled - revive found all packages which didn't have a documentation comment before. And tehre is A LOT of them. I updated some of them, but gave up at some point and just added them to exclude rules for now. - change lint-vulncheck to use `base` stage as base Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
I had to do several things: - contextcheck now supports Go 1.18 generics, but I had to disable it because of this kkHAIKE/contextcheck#9 - dupword produces to many false positives, so it's also disabled - revive found all packages which didn't have a documentation comment before. And tehre is A LOT of them. I updated some of them, but gave up at some point and just added them to exclude rules for now. - change lint-vulncheck to use `base` stage as base Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
I have some false positives on the code, which is not in my control. Can you stop analysis, if the error occurs in 3rd party libraries?
Example
This is source of
ParseString
, still does not accept context, but is already in 3rd party code:https://github.com/lestrrat-go/jwx/blob/develop/v2/jwt/jwt.go#L87
And here is code of
parseBytes
which does not accept context, but has variable namedctx
.https://github.com/lestrrat-go/jwx/blob/develop/v2/jwt/jwt.go#L158
Error
The code above is causing this issue
The text was updated successfully, but these errors were encountered: