Bug#968566: ITP: ruby-puma-worker-killer -- kill memory leaking puma workers

[Pirate Praveen <praveen@onenetbeyond.org>]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen <praveen@debian.org>

* Package name : ruby-puma-worker-killer
Version : 0.1.1
Upstream Author : Richard Schneeman
* URL : https://github.com/schneems/puma_worker_killer
* License : Expat
Programming Lang: Ruby
Description : kill memory leaking puma workers
Memory leaks in web code can be checked using puma_worker_killer.
.
When there is a memory leak in a code, finding and plugging it can be a
herculean effort. Instead what if processes are just killed when they 
got to
be too large? The Puma Worker Killer does just that. It is similar to 
Unicorn
Worker Killer but for the Puma web server.
.
Puma worker killer can only function cluster mode or hybrid mode 
(threads +
worker cluster) is enabled. If only using threads (and not workers) 
then puma
worker killer cannot help keep memory in control.

This is a dependency of gitlab 13.x (gitlab switched to puma from 
unicorn as default).