badly-behaved client can deadlock server stopping about cmux HOT 3 OPEN

Adding the wg.Done() only helps me I guess because I know that the for loop inside serve ran at least once first.

from cmux.

An effective mitigation of this behavior is to set a non-zero SetReadTimeout. That timeout applies only while sniffing an appropriate mux, just after initial connection

from cmux.

Would it be reasonable to add a wg.Done() before returning the error on line https://github.com/soheilhy/cmux/blob/master/cmux.go#L165? For me this solution seems to work, but I do not know what other potential problems this might cause.

from cmux.