-
Notifications
You must be signed in to change notification settings - Fork 37
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
[feature] Add Tzkt status to the indexer warning #327
Comments
Thanks I reformulated it into a request since I think we only check one endpoint and we might probably use a better approach like maybe something like cachet that hooks in docker or something like that Cc @Zir0h 😊 |
That's normal, we're currently on the public tzkt as I'm cleaning up the teia tzkt database. :) //edit: so not a bug |
Maybe rename |
That project seems to be quite dead :/ I installed uptime-kuma instead: https://status.teia.art/status/teia |
Oh lol, the status thingy was removed months ago in 8e79413 🤣 Maybe we can embed the bot status or uptime kuma status in the site somehow instead? |
Describe the bug
Teia TzKT server was delayed by 370 blocks, but Teia.art was not displaying an error message.
Reproduction
Go to teia.art and see no error banner
Answer bot on Discord shows error: https://discord.com/channels/908672304236625970/955606531200667748/1146571647139205142
Expected behavior
No response
Platform and versions
Console output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: