Implement ordering of PeerEndpoints in Peering #168
Closed
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
|
I expected the ordering to be applied to the model itself, so that any action on the queryset would be deterministic. Additionally, is there any issue with this ordering: |
mzbroch
force-pushed
the
mzbroch/ordering
branch
from
a88d3d4 to
e70bfbb
Compare
mzbroch
force-pushed
the
mzbroch/ordering
branch
from
e70bfbb to
993d305
Compare
Contributor
Author
|
Replaced by #169 |
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.
This PR implements ordering of PeerEndpoints in Peering
Closes #167