-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
fatal error: concurrent map writes #686
Comments
Found out that this is not a regression as this also happens in 1.1.1 stable.. :-( |
See golang/go#20270 |
@fpytloun thanks for reporting it. It certainly highlights that there's data race in aptly |
I've found a problem, and fix is ready. I'm looking for more places with same problem. Also I wonder if we can have easy way to produce load-test for aptly (nothing really complicated, simply exercising different APIs with concurrency of 4-5 would be more than enough) |
Great, is it already in latest nightly build, so I can test if it solved the issue? |
|
Good, seems this solved the issue :-) |
Thanks for reporting it! |
Detailed Description
Creating or updating a lot of publishes over aptly-api can sometimes result in
fatal error: concurrent map writes
exception.Full traceback:
Context
Possible Implementation
Your Environment
Docker image
tcpcloud/aptly-api/1.1.1-75-g9cb2a30
The text was updated successfully, but these errors were encountered: