-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Only call DisconnectNodes once per second #3421
Conversation
@codablock tests failing |
Tests are hopefully fixed now (had to call DeleteNode() without any locks held) |
This change is quite invasive for integration tests, as they all expect connections to be dropped ASAP. The next commits all try to fix the upcoming issues.
…info This ensures disconnected nodes don't appear for callers
|
@UdjinM6 yeah I noticed this as well, but decided to not fix it and leave it the way it is. Bitcoin also never fixed the missing cs_vNodes lock. It's semi-ok in this case, as Stop() first ensures that all network threads are stopped, so there is nothing left that could access the vectors. |
Well, we call |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
post-utACK
See individual commits. This PR also includes "Only run InactivityCheck once per second" from #3420 to avoid future merge conflicts. I'll rebase this PR after #3420 is merged into develop.