Introduce doneCh for ack error

[wolfstudy]

Signed-off-by: xiaolongran [email protected]

Motivation

In #775 and #776, we support the error information that may occur when the Go SDK side processes the Ack Command, but there is a bug in this implementation. We do not wait for the error information to return directly, so the error obtained in the Ack interface will always be nil.

Modifications

• Introduce doneCh to wait for the information of ack error to return

[liangyuanpeng]

I'm not sure if deleting A was the right choice.

[wolfstudy]

@freeznet PTAL thanks

[xiaofan-luan]

hi @wolfstudy , what would happen if currently we don't wait for ACK but broker side failed to ack?
If we get the error response how do we suppose to handle it?

[wolfstudy]

hi @wolfstudy , what would happen if currently we don't wait for ACK but broker side failed to ack? If we get the error response how do we suppose to handle it?

Here we can look at two situations:

1. If the location of the ack error is an error in the Go SDK, then we can now catch the error and try to call the ack interface again
2. If the ack error information is returned by the Broker, it means that the Broker has an error in processing the ack, and we can also try to ack again, but in general, we may need to further confirm why the Broker side failed and whether it conforms to the predetermined logic.