Reduce number of holepunching attempts when no direct connection exists #3906
+10
−1
Conversation
This file contains hidden or 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
DXist
force-pushed
the
feature/backoff_holepunching
branch
from
d6a3adb to
f7faefe
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
I've attempted to implement issue #3463 using the 'grok-code-fast-1' model without doing any manual changes.
Breaking Changes
Notes & open questions
Also asked the LLM to generate a demo example with a locally running client peer sending data to a local server peer via local relay. Blocked direct traffic between peer IPs. Only the first request was relayed and received a response; other requests timed out.
Let me know if you want me to include the example demo in the PR.
Change checklist