There's a report from users that indicates a CLI client can hang at the following spot:
At the same time the server has already progressed to the following state:
The issue appears to be that the server thinks it has sent the server's identity (CliProtocol2.Handler2.run() line 62) but the client is still waiting for it. The problem is reported as
always sporadically reproducible.
I'm failing to reproduce this problem locally. If other people see this problem, please report that here.