Closed jason-fox closed 5 years ago
Files with Coverage Reduction | New Missed Lines | % | ||
---|---|---|---|---|
logic.js | 17 | 82.18% | ||
<!-- | Total: | 17 | --> |
Totals | |
---|---|
Change from base Build 6: | -6.1% |
Covered Lines: | 214 |
Relevant Lines: | 250 |
PR looks good to me, except pm2 part. Why to use a process manager taking into account that we are using docker? docker-compose/docker swarm has support for restarting dead or unhealthy containers. Moreover, docker-compose/swarm allows you to configure restart policy, how to detect if the container is unhealthy, and so on. By using pm2 in the proposed way (not providing a way for configuring pm2), we are fixing the behaviour removing flexibility and not adding any feature.
In fact, some of the bugs FICODES has fixed on the IoTAgents are related to having IoTAgents entering in zombie mode (process running but not working as expected) problems that were not fixed by adding pm2. So, in my honest opinion, pm2 is not providing any advantage on the IoTAgents images.
@aarranz - I'll remove pm2
for now, but ideally I'd like to get a common way forward for this. I only added it in the first place for consistency with the IoT Agents.
Whether pm2
is a good thing, a bad thing or neither, I'd leave to the discussion thread
PR looks good to me, except pm2 part.
pm2
removed (at least for now) . Fixed: 0e5b9e5, 62a5b22
I don't know why coverage decreased, as you are not changing the code nor the tests...
This PR Updates the NGI Proxy Docker build to do the following