Added fallback_max_weight to Transact for sending messages to V4 chains#6643
Merged
franciscoaguirre merged 34 commits intomasterfrom Dec 5, 2024
Merged
Added fallback_max_weight to Transact for sending messages to V4 chains#6643franciscoaguirre merged 34 commits intomasterfrom
franciscoaguirre merged 34 commits intomasterfrom
Conversation
Contributor
Author
|
/cmd fmt |
Contributor
|
Command "fmt" has started 🚀 See logs here |
Contributor
|
Command "fmt" has finished ✅ See logs here |
Contributor
Author
|
/cmd prdoc --audience runtime_dev --bump major |
acatangiu
requested changes
Nov 29, 2024
Contributor
acatangiu
left a comment
acatangiu
left a comment
There was a problem hiding this comment.
See comments. Please also add an explicit Transact test from V5 chain -> V4 chain.
Contributor
Author
|
/cmd fmt |
Contributor
|
Command "fmt" has started 🚀 See logs here |
Contributor
|
Command "fmt" has finished ✅ See logs here |
Co-authored-by: Adrian Catangiu <[email protected]>
Co-authored-by: Adrian Catangiu <[email protected]>
Co-authored-by: Adrian Catangiu <[email protected]>
Contributor
Author
|
/cmd fmt |
Contributor
|
Command "fmt" has started 🚀 See logs here |
Contributor
|
Command "fmt" has finished ✅ See logs here |
|
All GitHub workflows were cancelled due to failure one of the required jobs. |
franciscoaguirre
had a problem deploying
to
release
GitHub Actions
Failure
franciscoaguirre
added a commit
that referenced
this pull request
Dec 5, 2024
…ns (#6643) Closes: #6585 Removing the `require_weight_at_most` parameter in V5 Transact had only one problem. Converting a message from V5 to V4 to send to chains that didn't upgrade yet. The conversion would not know what weight to give to the Transact, since V4 and below require it. To fix this, I added back the weight in the form of an `Option<Weight>` called `fallback_max_weight`. This can be set to `None` if you don't intend to deal with a chain that hasn't upgraded yet. If you set it to `Some(_)`, the behaviour is the same. The plan is to totally remove this in V6 since there will be a good conversion path from V6 to V5. --------- Co-authored-by: GitHub Action <[email protected]> Co-authored-by: Adrian Catangiu <[email protected]>
EgorPopelyaev
pushed a commit
that referenced
this pull request
Dec 9, 2024
#6778) Backport of #6643 to stable2412. We need it before the release so we have a good story with chains that haven't upgraded yet. --------- Co-authored-by: GitHub Action <[email protected]> Co-authored-by: Adrian Catangiu <[email protected]> Co-authored-by: Branislav Kontur <[email protected]>
Krayt78
pushed a commit
to Krayt78/polkadot-sdk
that referenced
this pull request
Dec 18, 2024
…ns (paritytech#6643) Closes: paritytech#6585 Removing the `require_weight_at_most` parameter in V5 Transact had only one problem. Converting a message from V5 to V4 to send to chains that didn't upgrade yet. The conversion would not know what weight to give to the Transact, since V4 and below require it. To fix this, I added back the weight in the form of an `Option<Weight>` called `fallback_max_weight`. This can be set to `None` if you don't intend to deal with a chain that hasn't upgraded yet. If you set it to `Some(_)`, the behaviour is the same. The plan is to totally remove this in V6 since there will be a good conversion path from V6 to V5. --------- Co-authored-by: GitHub Action <[email protected]> Co-authored-by: Adrian Catangiu <[email protected]>
dudo50
pushed a commit
to paraspell-research/polkadot-sdk
that referenced
this pull request
Jan 4, 2025
…ns (paritytech#6643) Closes: paritytech#6585 Removing the `require_weight_at_most` parameter in V5 Transact had only one problem. Converting a message from V5 to V4 to send to chains that didn't upgrade yet. The conversion would not know what weight to give to the Transact, since V4 and below require it. To fix this, I added back the weight in the form of an `Option<Weight>` called `fallback_max_weight`. This can be set to `None` if you don't intend to deal with a chain that hasn't upgraded yet. If you set it to `Some(_)`, the behaviour is the same. The plan is to totally remove this in V6 since there will be a good conversion path from V6 to V5. --------- Co-authored-by: GitHub Action <[email protected]> Co-authored-by: Adrian Catangiu <[email protected]>
This was referenced Jul 16, 2025
github-project-automation
bot
moved this from Todo
to Done
in [preview] release tracker
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes: #6585
Removing the
require_weight_at_mostparameter in V5 Transact had only one problem. Converting a message from V5 to V4 to send to chains that didn't upgrade yet. The conversion would not know what weight to give to the Transact, since V4 and below require it.To fix this, I added back the weight in the form of an
Option<Weight>calledfallback_max_weight. This can be set toNoneif you don't intend to deal with a chain that hasn't upgraded yet. If you set it toSome(_), the behaviour is the same. The plan is to totally remove this in V6 since there will be a good conversion path from V6 to V5.