"found" by the @discordapp troops the hard way: https://status.discordapp.com/incidents/62gt9cgjwdgf
pinging @zorkian who pointed it out to me.

trivial to repro, this is against a 3.3.13 on fedora-31.

$ etcdctl set /baa schnorp
$ etcdctl get /baa
schnorp
$ echo -ne 'PUT /v2/keys/baa HTTP/1.1\r\nHost: boo\r\nContent-Length: 123\r\n\r\n' | nc localhost 2379
HTTP/1.1 200 OK
...
$ et

What happened

Output generated from immuclient commands includes an additional blank line

e.g.

> ./immuclient set k0 v0
tx:		1 
key:		k0 
value:		v0 
hash:		6930a890518dad8804ffcee19d0c0759c4a31040612db8ea12beb7f7231047a0 

>

What you expected to happen

>./immuclient set k0 v0
tx:		1 
key:		k0 
value:		v0 
hash:		6930a890518dad8804ffcee19d0c0759c4a3104

Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.

This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients