Skip to content

Fix/deploy find server by port - #476

Merged
dkackman merged 2 commits into
developfrom
fix/deploy-find-server-by-port
Sep 26, 2026
Merged

dkackman merged 2 commits into
developfrom
fix/deploy-find-server-by-port

Conversation

@dkackman

Copy link
Copy Markdown
Owner

No description provided.

dkackman and others added 2 commits September 26, 2026 13:12
On macOS the Homebrew interpreter shows up in ps as .../MacOS/Python, so
pgrep -f 'python -m dw\.serve' finds nothing and a deploy starts a second
server on a port that's taken. Match what listens on DW_PORT instead
(lsof), falling back to the old pgrep where lsof is missing. Same result
on lem, where one server runs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dc05ab4 made every check ask what listens on DW_PORT. dw.serve imports
torch for seconds before it binds, so the startup loop saw an empty port
and reported 'exited during startup' on every deploy. Keep the port for
choosing what to stop, wait on the pids actually signalled (uvicorn closes
its socket early in a graceful shutdown), and judge startup by the process
(pgrep -i, so Homebrew's .../MacOS/Python matches too).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@dkackman
dkackman merged commit d21271d into develop Sep 26, 2026
11 checks passed
@dkackman
dkackman deleted the fix/deploy-find-server-by-port branch September 26, 2026 20:20
@dkackman dkackman mentioned this pull request Sep 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant