Skip to content
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

Open
2 tasks done
carlosala opened this issue Dec 17, 2024 · 4 comments
Open
2 tasks done

XcmPallet.execute weight is too high #6918

carlosala opened this issue Dec 17, 2024 · 4 comments
Assignees
Labels
I2-bug The node fails to follow expected behavior. I10-unconfirmed Issue might be valid, but it's not yet known.

Comments

@carlosala
Copy link

Is there an existing issue?

  • I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

  • This is not a support question.

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.

fn execute() -> Weight {
// Proof Size summary in bytes:
// Measured: `0`
// Estimated: `0`
// Minimum execution time: 18_446_744_073_709_551_000 picoseconds.
Weight::from_parts(18_446_744_073_709_551_000, 0)
.saturating_add(Weight::from_parts(0, 0))
}

Steps to reproduce

No response

@carlosala 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
@bkontur
Copy link
Contributor

bkontur commented Dec 17, 2024

@carlosala thank you, we probably forgot to regenerate weights for execute, it was allowed here: #3930, 18_446_744_073_709_551_000 is the Weight::MAX, I will open PR with new weights

@carlosala
Copy link
Author

Thanks Branislav!

@bkontur bkontur self-assigned this Dec 17, 2024
github-merge-queue bot pushed a commit that referenced this issue Dec 18, 2024
Relates to: #6918

---------

Co-authored-by: command-bot <>
github-actions bot pushed a commit that referenced this issue Dec 18, 2024
Relates to: #6918

---------

Co-authored-by: command-bot <>
(cherry picked from commit 9da3394)
@bkontur
Copy link
Contributor

bkontur commented Dec 19, 2024

@carlosala the fix is ready and should be deployed on Westend today, will let you know when ready

@bkontur
Copy link
Contributor

bkontur commented Dec 19, 2024

@carlosala ah sorry, they just told me that the release is moved to Monday

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.
Projects
None yet
Development

No branches or pull requests

2 participants