-
Notifications
You must be signed in to change notification settings - Fork 1
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
Data race bug #17
Comments
Didn't got panic with |
I didn't get panic with
|
Anyway, this is a valid issue (even if the chances of getting panic are minimal (checked with |
Did you run the tests or the mirror command? I don't get the race while running the tests but I get it when running the command, i.e. the actual production code. This also happens with Go 1.20.4. |
I switched to Go 1.20.4 and I'm still getting the race condition with that Go version as well. Here's a session where I'm running mirror on its own code. This time I'm building the mirror command from the main branch instead of installing it from the latest tag.
|
Let me come back with a bit refactored version, ok? |
Sure, no stress from me. I just wanted to show that I can reproduce the issue with Go 1.20 since there were two people saying they couldn't. I'm glad you're looking into it and reply fast. Not every open source project where you get that kind of response. I hope I can use mirror as part of golangci-lint soon. |
sidenote: feeling weird, considering I am now 2km from the zero line. calm day, with no shelling, has an LTE signal and can focus. |
hi, @hansgylling can you try the current head? |
Yes, I have now tried the latest commit on main many times on several code bases and I can't reproduce the data race anymore. I say this bug is resolved. |
This linter has a data race bug, easily detected by installing the command with the -race flag.
The text was updated successfully, but these errors were encountered: