-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fatal error: concurrent map writes #612
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
I just encountered exactly the same error with an identical stack-trace. $ golangci-lint --version
golangci-lint has version 1.17.1 built from 4ba2155 on 2019-06-10T09:07:35Z
$ go version
go version go1.12.5 darwin/amd64 |
As suggested in #622, given this has been addressed it could be worth closing the issue. 🙂 |
Hi, thank you for reporting, it's fixed in v1.18.0 release |
I am seeing same issue on
|
@gaurav-dalvi can you attach new logs/output please? |
@jirfag I'm also having the same issue intermittently on v1.23.8 error log: |
@jirfag I am facing the same issue with v1.27.0. The crash log (attached) points to this line and indeed there is a map being written to by multiple goroutines when creating the FilenameUnadjuster. |
Thank you for the error log @michaljemala, your analysis was indeed spot on. Have opened a PR that should address the issue in #1192. |
I am reclosing this issue now that the latest report has been addressed. If you encounter any new concurrent map write errors please open a new issue. 🙂 |
Hi, I got the error in 1.45.2:
|
I too got the error
|
Could we re-open this please? |
The bug still exists (version 1.54.2), @Helcaraxan
|
Given that this is very likely a completely different bug than the original one I would recommend opening a new issue. The error message is a generic Golang one, so even if it's the same it does not mean that it's the same bug instance inside golangci. I am unable to address this myself for the next few months in any case. |
Running linter in gilab ci
golangci-lint:v1.17
go 1.12
err log:
golangci.log
.golangci.yml:
The text was updated successfully, but these errors were encountered: