pallet-xcm: fix weights for all XTs and deprecate unlimited weight ones #3927
pallet-xcm: fix weights for all XTs and deprecate unlimited weight ones #3927acatangiu merged 6 commits intoparitytech:masterfrom
Conversation
Deprecate extrinsics that don't specify WeightLimit, remove their usage across the repo. Signed-off-by: Adrian Catangiu <adrian@parity.io>
|
bot bench cumulus-assets --runtime asset-hub-westend --pallet pallet_xcm |
|
@acatangiu https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/5719983 was started for your command Comment |
…=asset-hub-westend --runtime_dir=assets --target_dir=cumulus --pallet=pallet_xcm
|
@acatangiu Command |
svyatonik
left a comment
There was a problem hiding this comment.
Why pallet::weight attribute is removed at all from most of calls. Does it mean that the weight is now zero => near to zero fee + ability to create overweight block. I'm probably missing something important, just caught my eye
It is replaced by ::WeightInfo here. The default weight fn is fn with same name in There are some places where I kept |
svyatonik
left a comment
There was a problem hiding this comment.
Ok, cool stuff! Didn't knew we can do weight definitions in the #[pallet::call(..)]
…es (#3927) Fix "double-weights" for extrinsics, use only the ones benchmarked in the runtime. Deprecate extrinsics that don't specify WeightLimit, remove their usage across the repo. --------- Signed-off-by: Adrian Catangiu <adrian@parity.io> Co-authored-by: command-bot <>
…es (paritytech#3927) Fix "double-weights" for extrinsics, use only the ones benchmarked in the runtime. Deprecate extrinsics that don't specify WeightLimit, remove their usage across the repo. --------- Signed-off-by: Adrian Catangiu <adrian@parity.io> Co-authored-by: command-bot <>
Fix "double-weights" for extrinsics, use only the ones benchmarked in the runtime.
Deprecate extrinsics that don't specify WeightLimit, remove their usage across the repo.