-
-
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 Incompatibility with newer versions of Go? #663
Comments
I am having same issue |
Same here ☝️ |
same |
Rebuild golangci-lint with go 1.13 :-) |
This is a duplicate of #659. |
Can a maintainer release a new version built with go 1.13? The suggested CI method from the README is broken |
Hi, |
I ran into the same problem, updated to 1.19.0 just now, but the errors remain.
Am I doing something wrong? |
Please make a new issue with —version output |
My bad! I had a |
@tpounds of all Github issues related to this problem, this one is the most helpful: contains clear description of error and solution, maybe it's not quite "invalid" as end of thread suggests. |
@temoto Agreed. I must have incorrectly categorized this when I was traiging the backlog of open issues. I've updated this issue with a more appropriate label. |
I'm running version Go v1.13 and GoLangCI-Lint v1.17.1.
.golangci.yml:
goconfig.txt
Go Version: go1.13 darwin/amd64
I'm experiencing some encoding issues when I run GoLangCI-Lint against my code.
It looks like the linter is raising issue with the Go standard libraries (strings, fmt, etc.).
*golangci-lint run output
main.go:1: /usr/local/go/src/strconv/quote.go:405:12: ValidString not declared by package utf8 (typecheck)
main.go:1: /usr/local/go/src/bytes/reader.go:98:18: DecodeRune not declared by package utf8 (typecheck)
package main
pkg/cpu/cpu.go:1: /usr/local/go/src/fmt/scan.go:1200:16: DecodeRuneInString not declared by package utf8 (typecheck)
package ------
pkg/------/------.go:1: /usr/local/go/src/path/match.go:200:15: DecodeRuneInString not declared by package utf8 (typecheck)
The text was updated successfully, but these errors were encountered: