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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
statement-distribution: fix filtering of statements for elastic parachains #3879
statement-distribution: fix filtering of statements for elastic parachains #3879
Changes from 3 commits
e3b5192
01ceb3b
5ed7841
5f0872f
034b61a
9c91193
f87a624
70213c5
4c66001
21ae63d
e923dac
27ee145
be1a2c7
b9f1afc
17c4025
a185390
39f480d
d14384c
9de1a04
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, first (not introduced here): I find the name of this function vastly misleading as it does not fetch anything.
Second, why are we iterating only keys of the claim queue to fetch the actual element for each key, instead of iterating key/values to begin with?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to reuse the fn, but you are right, it is actually useless in this case. A wrapper for this BTreeMap with a method like
iter_claims(depth: BlockNumber)
returning an iterator over(core_index, para)
so we can lookup as far into the future as the lookahead param/ async backing settings allow.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tdimitrov wdyt ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#3950