-
Notifications
You must be signed in to change notification settings - Fork 157
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
GET /blocks/15426018 no results 500 error #1138
Labels
I2 - Bug 🐜
Sidecar has a bug
Comments
Hey @xiaochisAmber, thanks for reporting this issue. I was able to reproduce this on Kusama and looking into solutions right now. |
@TarikGul Hello, is it normal that the weight structure has changed after the update
after
|
@vae520283995 Yes, in Polkadot Release v0.9.31 a storage size ( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried both my own deployed nodes and third-party nodes, but could not get the results
curl localhost:8080/blocks/15426018
{"code":500,"message":"createType(RuntimeDispatchInfo):: Struct: failed on weight: {"refTime":"Lookup9","proofSize":"Lookup9"}:: Struct: Cannot decode value 27549795 (typeof number), expected an input object, map or array","stack":"Error: createType(RuntimeDispatchInfo):: Struct: failed on weight: {"refTime":"Lookup9","proofSize":"Lookup9"}:: Struct: Cannot decode value 27549795 (typeof number), expected an input object, map or array\n at createTypeUnsafe (/usr/src/app/node_modules/@polkadot/types-create/cjs/create/type.js:67:18)\n at TypeRegistry.createTypeUnsafe (/usr/src/app/node_modules/@polkadot/types/cjs/create/registry.js:295:46)\n at RpcCore._formatOutput (/usr/src/app/node_modules/@polkadot/rpc-core/cjs/bundle.js:381:21)\n at RpcCore._formatResult (/usr/src/app/node_modules/@polkadot/rpc-core/cjs/bundle.js:209:27)\n at callWithRegistry (/usr/src/app/node_modules/@polkadot/rpc-core/cjs/bundle.js:235:19)\n at runMicrotasks ()\n at processTicksAndRejections (node:internal/process/task_queues:96:5)","level":"error"}
curl -X GET \
The text was updated successfully, but these errors were encountered: