-
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
500 received for two blocks #1293
Comments
Okay cool, so for those public instances it looks like its an easy fix. They are currently on 14.5.2, they just need to be bumped to the most recent version: 17.0.0 and they should work fine. I was able to confirm it locally |
Thanks, it's been updated! Sorry for the noise. |
Hi, I'm reopening this issue because I'm seeing a 500 error on a new range of blocks and I understand the sidecars are on the most recent release. Issues start at block 15976986 and end at block 15978187. Here is a sample error message:
The nodes it's connected to are on 0.9.43, the latest polkadot release. https://polkadot-public-sidecar.parity-chains.parity.io/blocks/15978187 Thanks for any help! |
Closing in favor of #1299. If there is ever an issue with the public instances, please feel free to reopen this. |
Description
When attempting to access two particular blocks on Kusama there is an error.
https://kusama-public-sidecar.parity-chains.parity.io/blocks/18062770
https://kusama-public-sidecar.parity-chains.parity.io/blocks/18062771
Steps to Reproduce
See above links. If either of these blocks are included in a range query, the entire thing will also return a 500.
Expected vs. Actual Behavior
The block info should be correctly retrieved, just like all of the other blocks.
The text was updated successfully, but these errors were encountered: