-
Notifications
You must be signed in to change notification settings - Fork 27
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
blockchain: Avoid deadlock with additional locking #156
Conversation
The Travis failure is a false positive which is fixed in PR #127 |
pleeease can you just make sendNotification async so that
|
Probably! I really didn't investigate the logic much in this, just made the patch due to the race detector alert. Leave it open for now, I'll see if there is any reason why not to. |
@cjdelisle Not 100% sure if we can - see btcsuite#1563 for the kind of problems mainline has and we don't, and the behavior during deep/extended reorg is a bit of complex. Also btcsuite#1492 and btcsuite#1660, etc. GCash guys have similar changes to what I came up with at gcash/bchd#308 - I'd sort of feel better with this in place until I can get the test harness fixed and can run full regtestnet with the race detector on, and also because I know we had some extended reorg on the chain the other day and my node with these patches made it through and some of the gridnodes running older software crashed ... but recovered after restart. Fixing up the test harness is going to high priority for me, so I can more easily test these edge cases, especially for some of the more invasive changes I have in testing like the UDP FBT, etc. |
|
|
Found via race detector