Issue 952 operational dispatch class #960
Open
Conversation
This file contains 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
…ls (galacticcouncil#952) This commit changes the dispatch class to operational for critical transactions across: - `pallet_transaction_pause::pause_transaction` - `pallet_omnipool::set_asset_tradable_state` - `pallet_stableswap::set_asset_tradable_state` This ensures these important extrinsics can bypass block weight limits and be executed promptly. Additionally, operational-class tests have been introduced to verify behavior both under normal and operational conditions. The new integration tests cover scenarios to ensure that these calls function as intended, providing better resiliency and control over the execution of critical operations.
sylvaincormier
force-pushed
the
issue-952-operational-dispatch-class
branch
from
d2a6815 to
65b6d48
Compare
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.
This PR addresses the changes discussed in #952, introducing operational dispatch classes for the specified extrinsics:
As requested, I’ve ensured these critical calls are now dispatched with operational priority, allowing them to ignore block weight limits. Following your guidance, I’ve checked for potential side effects and confirmed that the operational class integration behaves as intended.
To validate these modifications, I ran a series of integration tests, including:
All tests passed successfully, as shown in the attached screenshot. The results indicate that the operational dispatch works as expected and doesn’t introduce unintended behavior.
Please let me know if you have any further feedback or if there are additional changes you’d like to see.
I appreciate your time reviewing this contribution and look forward to your input.