This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
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.
Two bugfixes:
When
addresses
is empty, we shouldn't just return at the beginning, as we need to erase the previous addresses.insert
is reallyinsert_or_replace
, similar to whatHashMap::insert
does. InsertingVec::new()
should remove the previous value.When an authority says it has a certain
PeerId
, we remove thatPeerId
from any previous authority. If this previous authority had multiple addresses (with the samePeerId
) we will callself.peer_id_to_authority_id.remove(&peer_id)
multiple times with the same value inpeer_id
. This is fine, but the debug assert just below (debug_assert!(_old_auth.is_some());
) is wrong, as it will fail the second time.Fix paritytech/polkadot#2998