Deduplicate dmp #24
Merged
Deduplicate dmp #24
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
shaunxw
reviewed
Mar 3, 2022
shaunxw
approved these changes
Mar 8, 2022
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.
when testing AcalaNetwork/Acala#1712 which send two xcm, recipient parachain get two dmp messages from relaychain. this is because
dmp_contentsnot deleted, thus causing duplicate mssages.the deduplicate condition is based on
to_para_id,relay_block_numberandmsg, this means relaychain can only send one same msg to one parachain in one block. it may make sense in testcase.