Andrushika opened a new pull request, #72564: URL: https://github.com/apache/airflow/pull/72564
## Why Follow-up of #71241: `breeze start-airflow --dev-mode` fails early when port 5173 or 5174 is taken. But the message only says the port is in use. Users then need to run `lsof` themselves to see which processes hold the ports before they can stop them, which is a bit annoying. Most of the time it is just a stale Vite dev server left over from a previous breeze run. ## What Look up the listening process with psutil and print its PID and command line, plus a `kill <pid>` hint. If the listener cannot be found (for example no permission), the old message is kept. psutil is bumped to `>=6.0.0` because `Process.net_connections()` was added there. Before: ``` Cannot start UI development servers because the following local port(s) are already in use: 5173, 5174. Stop the processes using these ports and try again. ``` Now: ``` Cannot start UI development servers because the following local port(s) are already in use: 5173, 5174. Port 5173 is used by PID 5771: node /Users/andrewchang/Dev/github.com/airflow/airflow-core/src/airflow/ui/node_modules/.bin/../vite/bin/vite.js —port 5173 —strictPort Port 5174 is used by PID 5793: node /Users/andrewchang/Dev/github.com/airflow/airflow-core/src/airflow/api_fastapi/auth/managers/simple/ui/node_modules/.bin/../vite/bin/vite.js —port 5174 —strictPort Stop the processes using these ports (for example kill 5771 5793) and try again. ``` related: #71241 --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Fable 5.1) Generated-by: Claude Code (Fable 5.1) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
