{ sc_panic!("Async call failed"); } } } } Contract B #[elrond_wasm::contract] pub trait ContractB { #[init] fn init(&self) {} #[endpoint(doNothing)] fn do_nothing( &self ) {} } We see on this transaction that the async call returned an error. Would you have an idea why? In particular, no matter the gas limit I provide, it is entirely consumed. Is it always the case that a callback entirely consumes the provided gas? - ElrondDevelopers"/> { sc_panic!("Async call failed"); } } } } Contract B #[elrond_wasm::contract] pub trait ContractB { #[init] fn init(&self) {} #[endpoint(doNothing)] fn do_nothing( &self ) {} } We see on this transaction that the async call returned an error. Would you have an idea why? In particular, no matter the gas limit I provide, it is entirely consumed. Is it always the case that a callback entirely consumes the provided gas? - ElrondDevelopers"/> { sc_panic!("Async call failed"); } } } } Contract B #[elrond_wasm::contract] pub trait ContractB { #[init] fn init(&self) {} #[endpoint(doNothing)] fn do_nothing( &self ) {} } We see on this transaction that the async call returned an error. Would you have an idea why? In particular, no matter the gas limit I provide, it is entirely consumed. Is it always the case that a callback entirely consumes the provided gas? - ElrondDevelopers"/> { sc_panic!("Async call failed"); } } } } Contract B #[elrond_wasm::contract] pub trait ContractB { #[init] fn init(&self) {} #[endpoint(doNothing)] fn do_nothing( &self ) {} } We see on this transaction that the async call returned an error. Would you have an idea why? In particular, no matter the gas limit I provide, it is entirely consumed. Is it always the case that a callback entirely consumes the provided gas? - ElrondDevelopers"/>
Sign up to join our community!
Please login to your account!
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
An error always consumes the whole gas. Not sure why you get an error though ????
You're returning an error with sc_panic in both branches