-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client HandleNext Behavior #11
Comments
Maybe this behavior is expected? If I add another goroutine that has a ticker to ping the server i stop receiving error messages. I also added a |
io.EOF and net.ErrClosed are special errors. We should always disconnect on receiving them since there is no more data to be expected after receiving them. Changes in #12. Feel free to test :) |
I ran into a bug with your
client.HandleNext()
function. When I setup a connection like you have in your examples after about a minuteclient.HandleNext()
starts blasting my terminal with EOF errors. According to the function docs if it has an error it should disconnect and go into a reconnect, but that's not the case. The code in question is:After about a minute it hits that
if err != nil
block and just spins out with EOFComments here indicate that it should fail and try to reconnect
natiu-mqtt/client.go
Line 56 in dc6618a
Here's the full code for reference:
The text was updated successfully, but these errors were encountered: