apply_authorized_force_set_current_code does not need to consume the whole block
#9202
Conversation
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
…e whole block There is no need that this dispatchable consumes the full block as this is just writing the given value to storage. On a chain this is done, because the runtime changes and thus, a lot of stuff potentially changes. In the case of the relay chain only on parachain changes and not the relay chain runtime itself.
bkchr
added
the
T8-polkadot
|
/cmd prdoc --audience runtime_user --bump patch |
bkontur
approved these changes
Jul 15, 2025
bkontur
added
A4-backport-stable2503
|
All GitHub workflows were cancelled due to failure one of the required jobs. |
acatangiu
approved these changes
Jul 15, 2025
|
Created backport PR for
Please cherry-pick the changes locally and resolve any conflicts. git fetch origin backport-9202-to-stable2503
git worktree add --checkout .worktree/backport-9202-to-stable2503 backport-9202-to-stable2503
cd .worktree/backport-9202-to-stable2503
git reset --hard HEAD^
git cherry-pick -x 607a1b24b7902a657426ce2412e316a57b61894b
git push --force-with-lease |
paritytech-release-backport-bot bot
pushed a commit
that referenced
this pull request
Jul 15, 2025
…e whole block (#9202) There is no need that this dispatchable consumes the full block as this is just writing the given value to storage. On a chain this is done, because the runtime changes and thus, a lot of stuff potentially changes. In the case of the relay chain only on parachain changes and not the relay chain runtime itself. --------- Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Branislav Kontur <bkontur@gmail.com> Co-authored-by: Adrian Catangiu <adrian@parity.io> (cherry picked from commit 607a1b2)
|
Successfully created backport PR for |
bkontur
added a commit
that referenced
this pull request
Jul 16, 2025
Backport #9202 into `stable2506` from bkchr. See the [documentation](https://github.com/paritytech/polkadot-sdk/blob/master/docs/BACKPORT.md) on how to use this bot. <!-- # To be used by other automation, do not modify: original-pr-number: #${pull_number} --> Co-authored-by: Bastian Köcher <git@kchr.de> Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Branislav Kontur <bkontur@gmail.com> Co-authored-by: Adrian Catangiu <adrian@parity.io>
bkontur
added
A4-backport-unstable2507
|
Created backport PR for
Please cherry-pick the changes locally and resolve any conflicts. git fetch origin backport-9202-to-stable
git worktree add --checkout .worktree/backport-9202-to-stable backport-9202-to-stable
cd .worktree/backport-9202-to-stable
git reset --hard HEAD^
git cherry-pick -x 607a1b24b7902a657426ce2412e316a57b61894b
git push --force-with-lease |
|
Backport failed for |
|
Created backport PR for
Please cherry-pick the changes locally and resolve any conflicts. git fetch origin backport-9202-to-stable2503
git worktree add --checkout .worktree/backport-9202-to-stable2503 backport-9202-to-stable2503
cd .worktree/backport-9202-to-stable2503
git reset --hard HEAD^
git cherry-pick -x 607a1b24b7902a657426ce2412e316a57b61894b
git push --force-with-lease |
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin stable2506
git worktree add -d .worktree/backport-9202-to-stable2506 origin/stable2506
cd .worktree/backport-9202-to-stable2506
git switch --create backport-9202-to-stable2506
git cherry-pick -x 607a1b24b7902a657426ce2412e316a57b61894b |
|
Successfully created backport PR for |
paritytech-release-backport-bot bot
pushed a commit
that referenced
this pull request
Jul 17, 2025
…e whole block (#9202) There is no need that this dispatchable consumes the full block as this is just writing the given value to storage. On a chain this is done, because the runtime changes and thus, a lot of stuff potentially changes. In the case of the relay chain only on parachain changes and not the relay chain runtime itself. --------- Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Branislav Kontur <bkontur@gmail.com> Co-authored-by: Adrian Catangiu <adrian@parity.io> (cherry picked from commit 607a1b2)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There is no need that this dispatchable consumes the full block as this is just writing the given value to storage. On a chain this is done, because the runtime changes and thus, a lot of stuff potentially changes. In the case of the relay chain only on parachain changes and not the relay chain runtime itself.