fix: PeX never sending local peers to remote peers #2984
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.

What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[X] Bug fix
[ ] New feature
[ ] Other, please explain:
What changes did you make? (Give an overview)
Fixed PeX (Peer Exchange) functionality to properly send local peers to remote peers. The issue was that
ut_pex.start()was never called and existing wire peers weren't shared with new PeX instances.Changes made:
ut_pex.start()afterwire.use(utPex())to start the PeX message timertest/node/pex.jsto verify functionalityWhich issue (if any) does this pull request address?
Fixes #2919
Is there anything you'd like reviewers to focus on?
Please review:
lib/torrent.js- ensuring existing wires are properly shared with new PeX instancesut_pex.start()call placement and timingtest/node/pex.js- verifies timer starts, peer sharing works, and cleanup is proper