Increase max_upward_message_size in RelayStateSproofBuilder to allow for larger XCM messages during testing.
#19
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
Increased the `max_upward_message_size` in `RelayStateSproofBuilder` to allow for larger XCM messages during testing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Increase the max_upward_message_size in RelayStateSproofBuilder from 256 to 1,048,576 to allow larger XCM messages during testing.
This change ensures that tests using the xcm-emulator can handle bigger messages without hitting the previous limit.
Integration
No special integration required. This is a runtime testing change and does not affect production behavior. Downstream projects can continue using RelayStateSproofBuilder as before; only test scenarios with large XCM messages will benefit.
Review Notes
Implementation is a simple increase of the constant max_upward_message_size.
No new dependencies introduced.
Example test scenario: sending an upward XCM message exceeding 256 bytes in xcm-emulator now passes.
No leftover TODOs; change is self-contained.
Checklist
My PR includes a detailed description as outlined in the "Description" and its two subsections above.
My PR follows the labeling requirements (ask maintainers to add the appropriate label if necessary).
Documentation updated if applicable (not required for this testing change).
Tests added or updated to verify the increased max_upward_message_size.