-
Notifications
You must be signed in to change notification settings - Fork 754
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
XcmPallet.execute
weight is too high
#6918
Labels
I2-bug
The node fails to follow expected behavior.
I10-unconfirmed
Issue might be valid, but it's not yet known.
Comments
carlosala
added
I10-unconfirmed
Issue might be valid, but it's not yet known.
I2-bug
The node fails to follow expected behavior.
labels
Dec 17, 2024
@carlosala thank you, we probably forgot to regenerate weights for execute, it was allowed here: #3930, |
Thanks Branislav! |
@carlosala the fix is ready and should be deployed on Westend today, will let you know when ready |
@carlosala ah sorry, they just told me that the release is moved to Monday |
dudo50
pushed a commit
to paraspell-research/polkadot-sdk
that referenced
this issue
Jan 4, 2025
Relates to: paritytech#6918 --------- Co-authored-by: command-bot <>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I2-bug
The node fails to follow expected behavior.
I10-unconfirmed
Issue might be valid, but it's not yet known.
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Description of bug
It seems that
XcmPallet.execute
weight in Westend is too high, around 18 million seconds of exection. This makes the extrinsic not available at all.polkadot-sdk/polkadot/runtime/westend/src/weights/pallet_xcm.rs
Lines 131 to 138 in 5b04b45
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered: