fix: bind ML API to 0.0.0.0 in Docker CI smoke test#847
Open
Rudra-clrscr wants to merge 3 commits into
Open
Conversation
The container's Flask process defaults to FLASK_HOST=127.0.0.1 (a deliberate secure default for bare-metal runs), so inside the CI container it never listens on an interface reachable through the -p 5000:5000 port mapping, and the smoke test's curl always times out. docker-compose.yml already sets FLASK_HOST=0.0.0.0 for the same reason; the CI workflow's docker run step needs the same override.
|
Someone is attempting to deploy a commit to the Aditya Sharma's projects Team on Vercel. A member of the Team first needs to authorize it. |
added 2 commits
July 14, 2026 04:55
main still has the pre-existing duplicate 'function App()' / unclosed JSX bug (only fixed inside open PR branches, never merged), so any fresh branch off main - including this one - fails 'vite build' during the frontend Docker image stage before the smoke test can even run. Bringing in the already-verified fix unblocks CI independent of merge order.
main's copy of this file starts with a stray '#Manipulation' line before the import statement - invalid JS that esbuild rejects. Only fixed inside the open frontend-eslint-errors PR branch, never merged to main. Same class of problem as the App.jsx duplicate-declaration fix: any branch cut fresh from main inherits this and fails 'vite build' during the frontend Docker image stage.
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
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.
The container's Flask process defaults to FLASK_HOST=127.0.0.1 (a deliberate secure default for bare-metal runs), so inside the CI container it never listens on an interface reachable through the -p 5000:5000 port mapping, and the smoke test's curl always times out. docker-compose.yml already sets FLASK_HOST=0.0.0.0 for the same reason; the CI workflow's docker run step needs the same override.