Near-sandbox with custom log length limits

[njelich]

I'm working on coverage for WASM smart contracts, and to do that I'm using a near-sandbox node.

To do that, one idea was to use logs to pass data, but logs have a length limit set in parameters.yaml config. I'm wondering how this can be changed for a near-sandbox instance?

Thanks!

[akhi3030]

CC: @ChaoticTempest. Could you help with this query please?

[njelich]

In the meantime I've found the EstimatorContext, which could be used for this.

There is an override in it that takes care of all the parameters that matter to me.

        // Override vm limits config to simplify block processing.
        runtime_config.wasm_config.limit_config = LimitConfig {
            max_total_log_length: u64::MAX,
            max_number_registers: u64::MAX,
            max_gas_burnt: u64::MAX,
            max_register_size: u64::MAX,
            max_number_logs: u64::MAX,

            max_actions_per_receipt: u64::MAX,
            max_promises_per_function_call_action: u64::MAX,
            max_number_input_data_dependencies: u64::MAX,
            max_length_storage_key: u64::MAX,

            max_total_prepaid_gas: u64::MAX,

            ..runtime_config.wasm_config.limit_config
        };
        runtime_config.account_creation_config.min_allowed_top_level_account_length = 0;

[ChaoticTempest]

Unfortunately, it doesn't seem like these parameters can be configured from either config.json or genesis.json in the home directory. So, one way to override these parameters is to define a new paramters.yaml file similar to how we have parameters_testnet.yaml already, but name it something like parameters_sandbox.yaml. We will then need to load it in core/runtime/config_store.rs where specifying ${sandbox-binary} inint --chain-id sandbox should point to the paramters_sandbox.yaml.