Status endpoint returns incomplete information about the last indexed block

[tk-o]

Version

0.9.10

Current behavior

GET /status mostly return incomplete information about the last processed block:

{"8453":{"block":null,"ready":false},"59144":{"block":{"number":6692961,"timestamp":1720789138},"ready":false}}

Sometime the response is complete, including the last processed block information:

{"8453":{"block":{"number":17778813,"timestamp":1722346973},"ready":false},"59144":{"block":{"number":7471797,"timestamp":1722347010},"ready":false}}

Expected behavior

GET /status always returns a complete response, including the last processed block information (block number, block timestamp), for example:

{"8453":{"block":{"number":17778813,"timestamp":1722346973},"ready":false},"59144":{"block":{"number":7471797,"timestamp":1722347010},"ready":false}}

Steps to reproduce

1. For a running indexer service, send HTTP request to GET /status endpoint on your running indexer service.
2. Observe the response.

Link to repository

https://github.com/namehash/ensnode/tree/main/apps/ensnode

Anything else?

I have been running two services with [email protected], feel free to get these nodes' status at:

• https://alpha.ensnode.io/status
• https://subgraph.ensnode.io/status

[kyscott18]

Hey @tk-o thanks for opening this. Have you noticed that the /status response reverts from having block information to have no block information for a network? At the beginning of indexing, Ponder is unable to determine what block the most recently indexed event is in until an event occurs in that network.

[tk-o]

Hard to say, but I remember, that while on v0.9.2 I could see status info loaded very quickly and being updated often enough for my use case.

What's interesting, /metrics enpodint serves correct data while /status endpoint does not.

Two tests:

curl -s https://alpha.ensnode.io/metrics | grep 'ponder_sync_block{' && curl -s https://alpha.ensnode.io/status

curl -s https://subgraph.ensnode.io/metrics | grep 'ponder_sync_block{' && curl -s https://subgraph.ensnode.io/status