paritytech-cmd-bot-polkadot-sdk[bot]
commented
1 week ago Created backport PR for stable2407:
-
5763 with remaining conflicts!
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin backport-5712-to-stable2407
git worktree add --checkout .worktree/backport-5712-to-stable2407 backport-5712-to-stable2407
cd .worktree/backport-5712-to-stable2407
git reset --hard HEAD^
git cherry-pick -x b230b0e32b8a12ab9b53b6a1040ba26a55704947
git push --force-with-lease
When running XCM emulated tests and seeing the logs with
RUST_LOG=xcmorRUST_LOG=xcm=trace, it's sometimes a bit hard to figure out the chain where the logs are coming from.I added a log whenever
execute_withis called, to know the chain which makes the following logs. Looks like so:There are already log targets for when UMP, DMP and HRMP messages are being processed. To see them, you have to use the log targets
ump,dmp, andhrmprespectively. SoRUST_LOG=xcm,ump,dmp,hrmpwould let you see every log. I prefixed the targets withxcm::so you can get all the relevant logs just by filtering byxcm. You can always use the whole target to see just the messages being processed.These logs showed the message as an array of bytes, I made them show a hexadecimal string instead since that's easier to copy in case you want to decode it or use it in another tool. They look like this now:
The HRMP and UMP ones are very similar.