-
Notifications
You must be signed in to change notification settings - Fork 369
XCM v5 support #6087
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @tmpolaczyk thanks for creating the issue, could you provide additional information 🙏🏻. What is the enviroment you are using, or maybe a code snipped so we can try to replicate the issue and investigate it |
It's a bit hard to reproduce, can't you just do the same as last time? If you need to reproduce, In this branch: https://github.com/moondance-labs/tanssi/commits/tomasz-wip-wip-stable2412
That last command with give the error. Full output: Logs
|
@valentinfernandez1 for some reason we upgraded to polkadot 2412 and our type generation is generating While I see that westend etc have also ugpraded to xcm v5, I dont see the types generated here contain the xcmv5 types, e.g., see:
We dont know what is the process or how can we help with this |
A bit more info, here is the metadata in json format: |
@valentinfernandez1 We are missing the V5 type def here:
|
@tmpolaczyk @girazoki sorry for the late response, I believe that with the PR that was merged with the Kusama types #6139 there is a fix necessary to address this problem. I think that should resolve the issue, the fix will land in a release yesterday. Additionally I am also adding the V5 types definitions and will try to merge that today so it also lands on tomorrows release. That should be enough to fix all the issues with XcmV5 compatibility. Will update this issue when the changes are live so you can test whether this is fixed. |
Should be addressed in latest release v15.10.1. Please give it a try and let me know so that we can close this issue |
Thanks @valentinfernandez1 , latest version seems to be working! However I see this suspicious diff in |
Nice catch!! Let me look deeper into this, it should be a |
Should be addressed by #6145, will quickly merge it and do a patch release. Should be live in about an hour |
Please try again with the new release v15.10.2 |
Updated to 15.10.2, is now a Vec so the fix works |
I get the same error as this issue:
#5811
I am using polkadot js 15.5.1
The text was updated successfully, but these errors were encountered: