Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Overcharging on limited_teleport_assets #7528

Merged

Conversation

gilescope
Copy link
Contributor

We count the teleported assets these days ( #6980 ) in the underlying do_teleport_assets function:

InitiateTeleport { assets: Wild(AllCounted(max_assets)), dest, xcm },

so we should use AllCounted rather than All for calculating the weight as we already do with the teleport_assets function's weight here:

assets: Wild(AllCounted(count)),

This brings the `limited_teleport_assets` weight into line with the
`teleport_assets` weight.
@gilescope gilescope added A0-please_review Pull request needs code review. C1-low PR touches the given topic and has a low impact on builders. D3-trivial 🧸 PR contains trivial changes in a runtime directory that do not require an audit. B1-note_worthy Changes should be noted in the release notes labels Jul 20, 2023
@gilescope gilescope added the T1-runtime This PR/Issue is related to the topic “runtime”. label Jul 20, 2023
@gilescope
Copy link
Contributor Author

bot merge

@paritytech-processbot paritytech-processbot bot merged commit 4776230 into master Jul 24, 2023
13 of 18 checks passed
@paritytech-processbot paritytech-processbot bot deleted the giles-limited-teleport-assets-weight-overcharged branch July 24, 2023 08:42
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A0-please_review Pull request needs code review. B1-note_worthy Changes should be noted in the release notes C1-low PR touches the given topic and has a low impact on builders. D3-trivial 🧸 PR contains trivial changes in a runtime directory that do not require an audit. T1-runtime This PR/Issue is related to the topic “runtime”.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants