This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[XCM] Multiple
FungiblesAdapter
s support +WeightTrader::buy_weight
more accurate error #6739[XCM] Multiple
FungiblesAdapter
s support +WeightTrader::buy_weight
more accurate error #6739Changes from 6 commits
b5945ee
ea32b57
9dc8504
a50366f
b1858f8
b43f230
4d83269
66de9cb
b47f25b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code like this is why we should actually figure out a better error reporting system for XCM, such as using
anyhow
orfailure
, because IIRC both of these crates allow chaining of errors, so you may chain errors together and have the ability to look into errors and see what the root cause is.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@KiChjang
This
buy_weight
returnsv3::XcmError
, so we probably shouldnt modify it now, right?Do you want to change error handling here or you mean it like future improvement, e.g. for v4?
If this change for
buy_weight
is blocking this PR, I can extract it to separate PRThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, no changes are necessary, I was making a general comment actually, but is definitely something that we should look into soon (one of the new hires can look into this).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this intended?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes,
ParaId
has different encoding thenSibling
,and e.g. everywhere in Cumulus there is used
SiblingParachainConvertsVia<Sibling,
and also everywhereParaId
is used by relaychain cfg likeChildParachainConvertsVia<ParaId,
I found it just by accident because of: https://github.com/paritytech/cumulus/pull/2167/files#diff-07287c62dd91150d975f7504bd14cc62d9889c44f7ba8ca44c30c03b05d5b071L389-R421 and I guess this was inspired by this example
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't. But the change is ok - just slightly more explicit about the intent.
(
Id
is imported asParaId
)