Kaocha-cljs2 appears to hang when no clients connect

[alysbrooks]

If no chui-remote clients are connected, Kaocha will wait forever. You can configure a timeout, but it's not enabled by default.

This is technically correct behavior and thus, arguably, not a true hang (which implies a deadlock or other invalid state), but it isn't very friendly to people setting it up for the first time.

[plexus]

Having a default timeout would make sense, sure.

[alysbrooks]

Another thing we could do is print a message after a shorter amount of time (or perhaps 1/2 of the timeout) that warns that no chui-client has connected yet.

[alysbrooks]

I'm biased, since I opened this issue, but I think this is a strong candidate to be one of our improvements to Kaocha-cljs2 in the near future.