Websocket disconnect issue about block-metrics HOT 5 CLOSED

Or maybe this is just the odd message when it hits the end of the blocks.

In such case, just clean up the error handling.

from block-metrics.

This is something I do not know how to solve well right now. Disconnection is caused by a server internal error.

sync: blocks for 11444: query tendermint: -32603: Internal error: failed response

This "internal" error is caused by a request for details of the block 11444. This block does not exist. Last block is probably 11443.

This happens, because there is no better way to get latest block. You can ask server what is the last block height, but by the time you get the response it might be outdated.

It is possible to solve this, I just hope for a solution that will not require a lot of coding. Right now finishing program with this error is not a blocker so I was not paying too much attention to it.

I have marked this issue as a bug as this is not how we expect this program to work.

from block-metrics.

I joined the club.

sync: blocks for 31785: query tendermint: -32603: Internal error: failed response

Our validator economic model is based on block metrics so, obviously, they're important. Moreover, part of the way we want to entice validators to join our program is by transferring their testnet quality scores to mainnet. (A quality score takes time to build.) All that to just fill you in on some of the on-goings on the business side. @kmw101, please make sure this issue is on your radar and has sufficient priority.

from block-metrics.

I think this can be "easily" fixed by capturing the last block where this failed and reopening then. As a hotfix.

from block-metrics.

this is closed via #14

from block-metrics.