Tag relay hops in relay implementations #1188
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
Stebalien
reviewed
Sep 16, 2021
Stebalien
approved these changes
Sep 16, 2021
marten-seemann
approved these changes
Sep 17, 2021
vyzo
force-pushed
the
feat/circuitv1-relay
branch
from
8e5996b to
243d07b
Compare
vyzo
force-pushed
the
feat/relay-tags
branch
from
bd7da41 to
9674b5c
Compare
|
rebased on master to resolve the (trivial) conflict; also made the hop tag constants private. |
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.
On top of #1186
In both relay v1 and v2 implementations, with a fixed value of 2. The value is purposefully very low, serving as an indicator to distinguish idle connections from connections with hop circuits during connection manager prunes.