Closed JimmyDeemo closed 1 year ago
Hello, thanks for filing an issue!
Is the affected machine using Foreman to manage the Rojo installation? This is a known issue with Foreman and some older versions of Aftman, but should not happen anymore on current releases.
Thanks for the response. 👍
As it happens, yes, we are using Foreman to manage Rojo at the moment. Is there a better work around for this other than killing the server? We have some slight dependencies on Foreman right now; moving to Aftman sh
This is a known limitation of Foreman. Sadly, the only options are to wait for the Foreman authors to fix it or to use Aftman instead.
One of our game designers is struggling with server issue for the Rojo studio plugin. It is very similar to this issue on the main Rojo repo but is easily reproducible with his setup.
lsof -i :34872
in terminal to see the service running.lsof -i :34872
again and notice that the service is still running.Address already in use
.kill -9 [PID]
to kill the running service.VSCode plugin version 2.1.2. MacOS Big Sur 11.6 (20G165)
Full error output;