Check port availability in Flutter before allowing engine execution
qdot opened this issue · comments
If the websocket port the engine listens on is taken, we error out either in rust or the the dart client right now. This isn't clear to the user. We should block starting the engine if the port isn't available, and let the user know that they need to either free the port or pick another one.