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
elastic scaling: add core selector to cumulus #5372
elastic scaling: add core selector to cumulus #5372
Changes from 4 commits
c6c166d
d7c595e
bcae16d
7b3594a
94bf1df
12aea2a
f1e2721
f9268dd
b825c22
7e2dc9a
48d19b9
6d0fbc1
e829934
e4478d1
920982f
ebf5e93
e5c366c
8305048
982ce7f
dec01b7
4c6fb64
6ab29d9
2c0c003
e8c7e96
a2c4d9b
67b17fa
b568cf4
010f7b9
08cd77d
b6d1fb1
99ff6dd
46fcf45
c268696
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.
This assumes that we already should be building on cores in the future if the claim queue is supported, even when not using the new candidate receipts.
I would keep the old behaviour and call
cores_scheduled_for_para_legacy
if v2 receipts are not enabled.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.
If we pass an offset of 0 here there should be no difference to the legacy version, correct?
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.
Actually we shouldn't be using the legacy version anymore.
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.
that's why I was proposing to use an offset of 0 if the parachain runtime doesn't have it configured
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.
With the introduction of this can we remove
availability_cores
from the interface? Did not check, but should not be used anymore now right?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.
yes, we could. But is there a good reason for that? There's still information that the availability-cores API contains that you cannot get elsewhere: like when a core is occupied or not. Maybe this will come in handy at some point in the future.