Rely on app database rather than replicate for prediction polling #64
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Thank you Aron! This looks great to me, and works on my tests |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently we're hitting the replicate backend every 500ms per prediction while waiting for the prediction to complete. This results in a lot of bandwidth between the client and replicate and eats up a fair amount of time.
This PR tweaks the logic to hit the database instead and return a
{id: string, status: "unknown"}string if no record is found (i.e we've not yet received the success hook from replicate).I also had to get this running locally so I've made some small tweaks to the error handling and extended the configuration to support a configurable image bucket
NEXT_PUBLIC_SUPABASE_IMAGES_HOSTso local images work as expected.