-
Notifications
You must be signed in to change notification settings - Fork 2.2k
peer: make ping manager send sync #9794
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
base: master
Are you sure you want to change the base?
Conversation
Important Review skippedAuto reviews are limited to specific labels. 🏷️ Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
In this commit, we make the ping manager sync blocking. This ensures that we don't start the ping timer until after we've actually sent out the ping on the wire. Otherwise, it's possible that if processing the normal outgoing queue is very delayed, that we expire the ping timer before we even send anything out to the remote peer. We also increase the msg size buffer. As otherwise, due to TCP head of the line blocking, we can still timeout the ping sends if we're just waiting for the remote party to receive the ping in the first place after a flurry of sends.
In this commit, we make the ping manager sync blocking. This ensures that we don't start the ping timer until after we've actually sent out the ping on the wire. Otherwise, it's possible that if processing the normal outgoing queue is very delayed, that we expire the ping timer before we even send anything out to the remote peer.