-
Notifications
You must be signed in to change notification settings - Fork 7
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
Race condition prevents library initialization ~1/100 times. #10
Comments
I also experienced this issue. Although for me, the bug manifested in a little bit different way. The initialization did not fail, but sometimes the I think the load is fast enough so It will be great if @rxp90 can review the PR above. Thanks. |
@rxp90 - I saw a new tag is created. For some reason, I still don't see the new version in maven. Any idea when it will get there? |
I think it's fixed now, it should be available soon |
hi @rxp90 just wondering if v1.1 is on maven yet: |
@Nanway It looks like I'll need to update the publishing steps to adapt to the changes made in maven central |
We've started using this at $WORK, and we've seen that sometimes initializing the library fails.
Throws this exception:
We've wrapped the initialization code in a loop as a stop gap, but it appears the problem is here:
The
this.deletes
collection is a ConcurrentHashMap, but thenew ArrayList()
it returns is not thread-safe. I believe switching thecomputeIfAbsent
to acompute
call that also adds the values to the ArrayList will fix it, but I'm not sure.The text was updated successfully, but these errors were encountered: