-
Notifications
You must be signed in to change notification settings - Fork 151
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
v11.3.8 not parse call parameters #835
Comments
hey @jqriyv, thanks for reporting this. Can you provide a reproducible example so I can check this specific example, and hopefully get a patch out for this. I would need:
|
|
Thanks again, I was able to reproduce it. Now just seeing how it was affected upstream. |
OK, I hope it can be repaired as soon as possible. This affects me, Thanks |
Yea this is a tricky one to debug because the parsing of the calls is a little complex, but I am working on getting this resolved, and am hoping to get a solution out for next weeks release. |
Ahhhh, i think i found the root of the problem :) |
This is great. I also try to resolve it myself, but the call of Polkadot is too flexible. Thank you very much. I hope this function can be restored in the next version. |
The above is patched via the linked PR. It just needs to get reviews and merged then a patch release will go through beginning of next week. |
v11.3.8 return block info, not parse call parameters
This is the return information of the previous version
Mind if you can parse all call parameters, such as proposal preimage
The text was updated successfully, but these errors were encountered: