Missing heart beat closing does not raise the correct notification

[Gsantomaggio]

Describe the bug

The close notification is incorrect when the client is closed due to a missing heartbeat.
So the client can't be reconnected. The client should consider the missing heartbeat as an error.

Reproduction steps

It should be enough to do the same: rabbitmq/rabbitmq-stream-dotnet-client#393

Expected behavior

Raise the socket closed error so the client can reconnect.

Additional context

No response

[gfanto]

Hi @Gsantomaggio, is this issue still present?

I was reviewing the code—specifically the Client.Close function (

rabbitmq-stream-go-client/pkg/stream/client.go

Line 474 in fa5203c

func (c *Client) Close() {

) and its invocation when heartbeats are missed (

rabbitmq-stream-go-client/pkg/stream/client.go

Line 445 in fa5203c

c.Close()

and noticed that Client.Close already sends the SocketClosed error. This made me wonder whether the issue has already been resolved.

If that’s the case, I’m not sure why this issue was opened after the relevant commit. Could you help clarify this?