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.
I had a hard time to debug the XCM weight issue caused by #6785. All the error message I got is XcmError::Barrier.
I understand why propagate error is hard but we need an alternative.
One way is to add enough logs to indicate why an error is occurred. I think we already drop logging in production build so it shouldn't have any overhead. And then in releases, it will be great to also make a production build with logging and we can use wasm override to use those runtime to debug errors.
For example, we could refactor this code to log weight limit and max weight and say it failed due to under weighted
In #6670, I'm adding a RejectReason to all barriers so that you know exactly why a particular XCM didn't pass the barrier. I could split out the PR so that we get the RejectReason logic in, and leave the blocking barrier implementation for later.
I had a hard time to debug the XCM weight issue caused by #6785. All the error message I got is
XcmError::Barrier
.I understand why propagate error is hard but we need an alternative.
One way is to add enough logs to indicate why an error is occurred. I think we already drop logging in production build so it shouldn't have any overhead. And then in releases, it will be great to also make a production build with logging and we can use wasm override to use those runtime to debug errors.
For example, we could refactor this code to log weight limit and max weight and say it failed due to under weighted
polkadot/xcm/xcm-builder/src/barriers.rs
Lines 95 to 105 in f1a45b3
The text was updated successfully, but these errors were encountered: