Fix: Have TzKt.Api do more retries for Database Schema before failing #1612
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🌮 Taqueria PR
🪁 Description
When we start the Sandbox, four containers start:
After starting, TzKt.sync will apply the database schema to postgres. TzKt.Api keeps checking this schema to make sure it can work with that document. It does this 30 times. This has been enough for their own setup (on a server, where they can start them separately and wait for sync to apply the schema) and on my machines.
But on some machines, this is not enough.
So here is our solution:
🪂 Pre-Merge Checklist (Definition of Done)
🚦 Required to merge:
🛩️ Summary of Changes
We release TzKt images in Ecad labs docker hub account and used it here
🎢 Test Plan
Please describe the testing strategy and plan for this PR. Keep this lightweight and anticipate any testing challenges
🛸 Type of Change