Today, VS Code became unresponsive. After closing and reopening VS Code, we noticed that the port 4200 was in use. I assumed that it was the development server of MODEL-AD that was still running in the background. One way to kill a process that uses a specific port is using the workspace command workspace-kill-port {port number}. This command failed because my assumption was incorrect: it was actually the Docker container of the OpenChallenges (OC) app that was running, and the kill command can't stop a container that is using a port. One way I'm trying to prevent this specific issue (port conflicts) is to assign different ports to different projects in the monorepo. We currently have multiple projects that use the default Angular port 4200. We will change this first next time we meet.
Changelogs
model-ad-configsrc/config/config.jsonsrc/config/config.json.templateReferences
Notes
Today, VS Code became unresponsive. After closing and reopening VS Code, we noticed that the port 4200 was in use. I assumed that it was the development server of MODEL-AD that was still running in the background. One way to kill a process that uses a specific port is using the workspace command
workspace-kill-port {port number}. This command failed because my assumption was incorrect: it was actually the Docker container of the OpenChallenges (OC) app that was running, and the kill command can't stop a container that is using a port. One way I'm trying to prevent this specific issue (port conflicts) is to assign different ports to different projects in the monorepo. We currently have multiple projects that use the default Angular port 4200. We will change this first next time we meet.