-
Notifications
You must be signed in to change notification settings - Fork 378
Support overweight messages in XCMP queue #799
Conversation
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 would like to see a test that tries to process an overweight XCM and then calls the service_overweight functionality.
pub fn migrate_to_v1<T: Config>() -> Weight { | ||
let translate = |pre: v0::QueueConfigData| -> super::QueueConfigData { | ||
super::QueueConfigData { | ||
suspend_threshold: pre.suspend_threshold, | ||
drop_threshold: pre.drop_threshold, | ||
resume_threshold: pre.resume_threshold, | ||
threshold_weight: pre.threshold_weight, | ||
weight_restrict_decay: pre.weight_restrict_decay, | ||
xcmp_max_individual_weight: super::QueueConfigData::default() | ||
.xcmp_max_individual_weight, | ||
} | ||
}; |
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.
Would it make sense to parameterize the migration function to take a xcmp_max_individual_weight
so that people can migrate to whatever config value they want?
Alternatively we'd want to expose some knob somewhere to update the queue config, no?
Maybe a candidate for a follow-up issue?
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.
added an issue: #801
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.
LGTM, I'll let Gav address the question in code
Looks reasonable. |
* Bump Cumulus, Polkadot, and Substrate Also bumps some other depenencies * Remove duplicate `polkadot` dependency * Update `service.rs` Changes related to: paritytech/cumulus#835 * Update `command.rs` * Add `AddressGenerator` config type From: paritytech/substrate#10521 * Allow Root to execute overweight XCMP messages From: paritytech/cumulus#799 * Add `header` argument to `collect_collation_info` From: paritytech/cumulus#882 * Update Cumulus and friends again * Add Fork ID to genesis config paritytech/cumulus#870 * Add `state_version` field paritytech/substrate#9732 * Add `MaxConsumers` config parameter paritytech/substrate#10382 * Update Substrate compatibility note in README
Implementation follows closely to the UMP overweight message handling, as seen here in this PR.
Fixes paritytech/srlabs_findings#145.