fix: connections can become stale when reconnecting #4310
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request
Checklist
Please conduct a thorough self-review before opening the PR.
Summary
Previously in some cases it was possible for connections to never become "stale" (preventing reconnections when inactive). Specifically, when we fail to connect to a node due to some authentication error, this would result us reconnecting to the node manually (rather than this being done by zmq internally), but this also reset activity for that node to "now" on every restart, preventing us from detecting the connection as stale. I changed the code to carry over any previous activity state when reconnecting, so inactive connections should now always enter "stale" state.
Writing a proper unit test for this is a bit cumbersome and I'm not sure if worth it, but I have tested this manually by changing some parameters and observing logs that the bug was present initially and that the new code fixes the incorrect behaviour.