JS-100 Allow the server to restart after failed status

[zglicz]

JS-100

Tested by hand with killing the node processes and waiting a minute to see that the server actually gets respawned. See logs:

 [2024-12-04T16:52:13.064] [sonarlint-analysis-engine] DEBUG sonarlint - Skipping the start of the bridge server as it failed to start during the first analysis or it's not answering anymore
..
 [2024-12-04T16:52:23.924] [sonarlint-analysis-engine] DEBUG sonarlint - Skipping the start of the bridge server as it failed to start during the first analysis or it's not answering anymore
..
 [2024-12-04T16:52:30.923] [sonarlint-analysis-engine] DEBUG sonarlint - Skipping the start of the bridge server as it failed to start during the first analysis or it's not answering anymore
..
 [2024-12-04T16:52:36.868] [sonarlint-analysis-engine] DEBUG sonarlint - Skipping the start of the bridge server as it failed to start during the first analysis or it's not answering anymore
..
 [2024-12-04T16:52:43.438] [sonarlint-analysis-engine] WARN sonarlint - No workDir in SonarLint
 [2024-12-04T16:52:43.439] [sonarlint-analysis-engine] DEBUG sonarlint - Setting deploy location to /Users/michal.zgliczynski/codes/SonarJS
 [2024-12-04T16:52:43.439] [sonarlint-analysis-engine] INFO sonarlint - 'sonar.nodejs.executable' is set. Skipping embedded Node.js runtime deployment.
 [2024-12-04T16:52:43.439] [sonarlint-analysis-engine] DEBUG sonarlint - Starting server
 [2024-12-04T16:52:43.439] [sonarlint-analysis-engine] DEBUG sonarlint - Creating Node.js process to start the bridge server on port 65465 
 [2024-12-04T16:52:43.439] [sonarlint-analysis-engine] INFO sonarlint - Running in SonarLint context, metrics will not be computed.
 [2024-12-04T16:52:43.439] [sonarlint-analysis-engine] INFO sonarlint - Using Node.js executable /Users/michal.zgliczynski/.nvm/versions/node/v22.9.0/bin/node from property sonar.nodejs.executable.
 [2024-12-04T16:52:43.439] [sonarlint-analysis-engine] DEBUG sonarlint - Checking Node.js version
 [2024-12-04T16:52:43.439] [sonarlint-analysis-engine] DEBUG sonarlint - Launching command /Users/michal.zgliczynski/.nvm/versions/node/v22.9.0/bin/node -v
 [2024-12-04T16:52:43.462] [sonarlint-analysis-engine] DEBUG sonarlint - Using Node.js v22.9.0.
 [2024-12-04T16:52:43.462] [sonarlint-analysis-engine] DEBUG sonarlint - Launching command /Users/michal.zgliczynski/.nvm/versions/node/v22.9.0/bin/node /Users/michal.zgliczynski/codes/SonarJS/package/bin/server.cjs 65465 127.0.0.1 /Users/michal.zgliczynski/codes/SonarJS true true false 
 [2024-12-04T16:52:44.125] [nodejs-stream-consumer] INFO sonarlint - Memory configuration: OS (36864 MB), Node.js (4144 MB).
 [2024-12-04T16:52:44.125] [nodejs-stream-consumer] DEBUG sonarlint - Starting the bridge server
 [2024-12-04T16:52:44.13] [nodejs-stream-consumer] DEBUG sonarlint - The bridge server is listening on port 65465
 [2024-12-04T16:52:44.134] [nodejs-stream-consumer] DEBUG sonarlint - The worker thread is running
 [2024-12-04T16:52:44.244] [sonarlint-analysis-engine] DEBUG sonarlint - Bridge server started on port 65465 in 805 ms
 

[vdiez]

I wonder if we should limit the restart to cases when the process ended due to lack of heartbeats. For that we would need to check output the node process. Thoughts?

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
62.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube