plugin: Enforce canonical LSPS ordering - #730
Merged
Merged
Conversation
cdecker
force-pushed
the
2026w23-lsps-ordering
branch
2 times, most recently
from
June 10, 2026 15:59
42a58ef to
bd267ff
Compare
cdecker
force-pushed
the
2026w23-lsps-ordering
branch
from
June 29, 2026 15:22
bd267ff to
d69fb17
Compare
We were randomly selecting an LSPS peer from the list of peers. Adding a canonical ordering, by their `node_id`, allows us to steer that selection more reproducibly.
cdecker
force-pushed
the
2026w23-lsps-ordering
branch
from
August 3, 2026 09:32
3235316 to
2ba5eb6
Compare
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
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.
We were randomly selecting an LSPS peer from the list of peers. Adding
a canonical ordering, by their
node_id, allows us to steer thatselection more reproducibly.