I understand there are some bugs and issues that can be contributed via PRs but would you really go as far to say that the whole code needs to be ditched and new implementation needs to be provided?
Glad to see some infrastructure diversity coming along. You know how hard Erik is working on DBSync and there are certainly some bugs to clean up. Overall, successful launch and much to do with cleanup
This time we were lucky, but what the next time? Yes, cardano-db-sync is part of the critical infrastructure and needs to be treated that way, but we as a community need to build alternative tools, as that is decentralization too.
Just keeping a log for future reference.
Today’s the day I realise we cannot rely on cardano-db-sync for our project. Another bump on the already bumpy road of writing stuff for cardano 😤
And I still aim we release in time.
Currently we can't show the correct status of wallets.
db-sync rolled back on all servers after it encountered a bug and since it's now rolling back to epoch start, yeah, it takes a while to catch up with the mainnet tip. 🙄
Due to a bug in db-sync we will be in maintenance mode for a while.
We are going to block this feature temporarily while we fix it in order to avoid confusion. The problem is caused by db-sync 11 which is maintained by IOHK. We are partnering with them to get this resolved as soon as possible in order to restore the service.
To all those that run cardano-db-sync and just hit the issue
Just run
ALTER DOMAIN lovelace
DROP CONSTRAINT lovelace_check;
and it will start working again
If you're reading this tweet and you don't know what cardano-db-sync is, then you don't have to worry about it.
🚨db-sync is rolling back to epoch start.
all exchanges, all explorers, services using db-sync are out of sync (and will be for a hour or so).
$ADA #cardano
