-
Notifications
You must be signed in to change notification settings - Fork 248
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
Update domain config items #3083
Conversation
Signed-off-by: linning <[email protected]>
…in config Signed-off-by: linning <[email protected]>
Signed-off-by: linning <[email protected]>
Signed-off-by: linning <[email protected]>
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.
Overall this looks reasonable to me, but I think someone more familiar should double-check.
max_bundle_weight, | ||
} = calculate_max_bundle_weight_and_size( | ||
MaxDomainBlockSize::get(), | ||
MaxDomainBlockWeight::get(), |
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 is not MAX
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.
Yeah, it is not a hard limit for the domain block (which is set to MAX in the domain runtime), it is used as hard limit for the bundle weight/size though.
Signed-off-by: linning <[email protected]>
Signed-off-by: linning <[email protected]>
Signed-off-by: linning <[email protected]>
This PR implements subspace/protocol-specs#22, includes changes of:
DomainConfig::target_bundles_per_block
fieldDomainConfig::max_block_size/weight
withDomainConfig::max_bundle_size/weight
Code contributor checklist: