Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
Hive sometimes becomes totally frozen, when client containers do not properly exit (nor respond).
See https://github.com/ethereum/aleth/issues/5243 and https://github.com/paritytech/parity-ethereum/issues/5571 . The current work-around is to either ssh into the machine and kill them, or to run a cron-job to kill any `aleth` or `parity` processes older than e..g 10 minutes.
It would be good if the simulator, when starting a new container, could specify a `max-lifetime` for the container. The hive framework would then kill the client container after the specified time, just as if the simulator killed it with a request.
Note: The kill-timers should not pile up indefinitely -- if we run 1000 containers within 10 minutes (and all exist within a short time), there should not be 1000 timers - so remove the timer when the container dies.
cc @vs77bb - can we get this bountied?