Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Pallet errors are not visible anywhere when submitted via XCM Transact #5394

Closed
haerdib opened this issue Apr 26, 2022 · 2 comments
Closed

Comments

@haerdib
Copy link

haerdib commented Apr 26, 2022

When submitting a transaction via the XCM Transact, errors happening within the relevant pallet are not shown anywhere:

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.

@dzmitry-lahoda
Copy link

is seems in progress with v3 paritytech/polkadot-sdk#887

@haerdib
Copy link
Author

haerdib commented Aug 31, 2022

Yes, that's it. Thanks a lot :)

@haerdib haerdib closed this as completed Aug 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants