forked from irungentoo/toxcore
-
Notifications
You must be signed in to change notification settings - Fork 284
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
refactor: Make some improvements to how often/when we announce a group #2348
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JFreegman
added
the
refactor
Refactoring production code, eg. renaming a variable, not affecting semantics
label
Oct 8, 2022
JFreegman
force-pushed
the
ngc_announce_fix
branch
2 times, most recently
from
October 12, 2022 17:57
8b56a49
to
1585048
Compare
sudden6
reviewed
Nov 12, 2022
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.
Generally looks good, just some documentation stuff
JFreegman
force-pushed
the
ngc_announce_fix
branch
from
November 12, 2022 14:05
1585048
to
f5c1120
Compare
sudden6
approved these changes
Nov 12, 2022
JFreegman
force-pushed
the
ngc_announce_fix
branch
9 times, most recently
from
November 25, 2022 15:31
b674660
to
a8b0516
Compare
Instead of announcing a group whenever our connection status changes, including when we gain or lose a TCP relay connection, we now only when our UDP status changes, or if our previously announced relay has gone offline. We also refresh our announcement 20 minutes regardless of any connection changes. change should vastly reduce the amount of unnecessary DHT traffic related to group announcements.
JFreegman
force-pushed
the
ngc_announce_fix
branch
from
November 25, 2022 15:56
a8b0516
to
7ee7720
Compare
Codecov Report
@@ Coverage Diff @@
## master #2348 +/- ##
==========================================
- Coverage 78.13% 78.08% -0.05%
==========================================
Files 141 141
Lines 31108 31114 +6
==========================================
- Hits 24306 24296 -10
- Misses 6802 6818 +16
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Instead of announcing a group whenever our connection status changes, including when we gain or lose a TCP relay connection, we now only announce when our UDP status changes, or if our previously announced TCP relay has gone offline. We also refresh our announcement every 20 minutes regardless of any connection changes (this is to rotate the TCP relay in case the chosen one is somehow broken).
This change should vastly reduce the amount of unnecessary DHT traffic related to group announcements.
This change is