Skip to content
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions cumulus/xcm/xcm-emulator/src/lib.rs
Original file line number Diff line number Diff line change
Expand Up @@ -1199,6 +1199,7 @@ macro_rules! decl_test_networks {
let mut sproof = $crate::RelayStateSproofBuilder::default();
sproof.para_id = para_id.into();
sproof.current_slot = $crate::polkadot_primitives::Slot::from(relay_parent_number as u64);
sproof.host_config.max_upward_message_size = 1024 * 1024;

// egress channel
let e_index = sproof.hrmp_egress_channel_index.get_or_insert_with(Vec::new);
Expand Down
14 changes: 14 additions & 0 deletions prdoc/pr_10313.prdoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
title: Increase `max_upward_message_size` in `RelayStateSproofBuilder`
doc:
- audience: Runtime Dev
description: |-
## Description

While testing different XCM messages via xcm-emulator, I noticed that the limit of 256 for `max_upward_message_size` in `RelayStateSproofBuilder` can be reached very easily.

I suggest increasing it to `1024 * 1024` so that we can have a good range for testing.
crates:
- name: cumulus-test-relay-sproof-builder
bump: patch
Comment thread
bkontur marked this conversation as resolved.
Outdated
- name: xcm-emulator
bump: patch
Loading