You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, block count cache ttl is a constant, defined by runtime environment variable. And the default value is relatively big: 2 hours.
On the newly spinned up instance of Blocskcout, it may cause the issue, that indexing progress banner may still persist, even if the chain already indexed in the Blockscout explorer.
The suggestion is to make ttl dynamically changed based on the number of blocks in the DB.
The text was updated successfully, but these errors were encountered:
Currently, block count cache ttl is a constant, defined by runtime environment variable. And the default value is relatively big: 2 hours.
On the newly spinned up instance of Blocskcout, it may cause the issue, that indexing progress banner may still persist, even if the chain already indexed in the Blockscout explorer.
The suggestion is to make ttl dynamically changed based on the number of blocks in the DB.
The text was updated successfully, but these errors were encountered: