You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
let actual_weight = match message_call.dispatch(dispatch_origin){
Ok(post_info) => post_info.actual_weight,
Err(error_and_info) => {
// Not much to do with the result as it is. It's up to the parachain to ensure that the
// message makes sense.
error_and_info.post_info.actual_weight
},
XCM Logs will simply report an xcm::execute_xcm_in_credit: result: Ok(()) even if the pallet call has failed. This makes it very hard to debug.
It would be very helpful if the error returned by the pallet would at least be logged somewhere. Or even more preferable: If the XCM execution would not result in an Ok(()), but in an Error instead… or an Ok with a corresponding error message in it, such that one can debug from the parachain side.
The text was updated successfully, but these errors were encountered:
When submitting a transaction via the XCM
Transact
, errors happening within the relevant pallet are not shown anywhere:polkadot/xcm/xcm-executor/src/lib.rs
Lines 347 to 353 in 9428d8c
XCM Logs will simply report an
xcm::execute_xcm_in_credit: result: Ok(())
even if the pallet call has failed. This makes it very hard to debug.It would be very helpful if the error returned by the pallet would at least be logged somewhere. Or even more preferable: If the XCM execution would not result in an
Ok(())
, but in anError
instead… or anOk
with a corresponding error message in it, such that one can debug from the parachain side.The text was updated successfully, but these errors were encountered: