Open
Description
Go version: 1.18
Hazelcast Go Client version: 1.4
Hazelcast server version: 5.2.x
Number of the clients:1
Cluster size, i.e. the number of Hazelcast cluster members: Viridan Dev
OS version : Windows
Expected behavior
When I provide wrong discovery token to the client, it freezes and, doesn't do anything.
Actual behavior
Wrong discovery token should be failed since there will be no valid address that is provided by Viridian coordinator.