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 in ACMEIssuer #195
Comments
Oh yeah, I think this is a known issue. There should be a TODO in the code. I'll look closer when I'm not mobile. Thanks! |
Okay, so it's not quite the same as the known issue, which was apparently fixed but I forgot that I fixed it. It's very similar though. Edit: But the second race IS a known issue and does have a TODO: comment: "Is this racey?" -- lol. So I guess it is. |
Thanks for the detailed report @zllovesuki -- should be fixed now. Would you be able to give it a try? 😃 |
can confirm that race detector is now happy 👍 |
Awesome!! Thanks for verifying. |
What version of the package are you using?
What are you trying to do?
Using certmagic with advanced setup to manage certificate automatically.
What steps did you take?
This is what I'm using to setup certmagic:
After the function returns, this is how I invoke certmagic to get certs:
The binary was compiled in docker with the
-race
flag, with pebble, test server from LE to not validate challenge (so all cert request will be approved, hence the NoopSolver).What did you expect to happen, and what actually happened instead?
Expectation: certmagic obtained certificate and the race detector is happy about it.
Reality: certmagic did obtain the certificate, but race detector complained about unsafe concurrent access:
How do you think this should be fixed?
(will update this section once I read through the code)
The text was updated successfully, but these errors were encountered: