-
Notifications
You must be signed in to change notification settings - Fork 256
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
Subxt parse kilt metadata failed. response: expected u32
, found u64
#369
Comments
+1 on this, I'm running into the same problem. |
The problem here appears to be that the The way I figure this out was to use
There is an upcoming PR which should allow you to use your own predefined type configuration for your runtime: #373. This likely won't be merged until next year since there is nobody around to review it, but you can try it out with that branch, and supply your own |
@ascjones could your provide an example on how to use the code generation with a custom config in a programatic way? |
I had a go at giving you the example code that I thought would suffice, but I wasn't able to make it work offhand and so I've filed #391. Alas @ascjones is unavailabel for a couple of weeks. I'll probably get the chance to dig into it more in the ocming days but at present it's not obvious what the best solution is! |
I believe that this has been addressed so I'll close the issue now, but please re-open if I was wrong! :) |
env:
test repo:
git repo:
https://github.com/atenjin/kilt-client
(https://github.com/atenjin/kilt-client/tree/try/subxt
)branch:
try/subxt
metadata: from endpoint
wss://peregrine.kilt.io/
directly, it's version is V14.and the metadata I get from the endpoint throught subxt-cli is in :
https://github.com/atenjin/kilt-client/blob/try%2Fsubxt/res/metadata.scale
subxt version:
78626eb5eef60b52fd199adb26a724e68c4fdb55
substrate version:
b9cafba3d0e7a5950ac78d81e4ab7f2074938666
replay method:
Then compile it, I get an error:
It seems not a custom type error, like not finding the right type path or else. So I'm confused for the converting type error.
The text was updated successfully, but these errors were encountered: