fix: cache yolox model in docker build to prevent 429 cloud run errors#4405
Open
MansiDakhale wants to merge 1 commit into
Open
fix: cache yolox model in docker build to prevent 429 cloud run errors#4405MansiDakhale wants to merge 1 commit into
MansiDakhale wants to merge 1 commit into
Conversation
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
No issues found across 1 file
Shadow auto-approve: would auto-approve. Pre-caches the yolox model in the Docker build to prevent runtime 429 errors. Bounded, beneficial build optimization; no behavioral, contract, or operational tradeoff needing human judgment.
Re-trigger cubic
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This PR resolves a deployment bottleneck where 429 Too Many Requests errors occur on Google Cloud Run when multiple container instances simultaneously attempt to download the yolox model weights at runtime.
The Fix:
I shifted the model download left into the build phase. By caching the yolox model during the Dockerfile build (alongside spaCy and TableTransformer), the model weights are now baked directly into the container image. This eliminates network dependencies at runtime and prevents rate-limiting crashes.
Related Issue
Closes #4110