Error all outstanding tokens at disconnection

If connected with cleansession false you could expect to get outstanding message confirmations after reconnecting, but actually this would only occur with QoS2 publishes at PUBREC, QoS1 and QoS2 after PUBREL will be assumed by the sender to have been received, this will cause tokens to hang. This change causes all outstanding tokens at disconnection time to be completed as errored.

Author: alsm

Diff for: client.go

@@ -437,9 +437,7 @@ func (c *client) internalConnLost(err error) {
 		c.closeStop()
 		c.conn.Close()
 		c.workers.Wait()
-		if c.options.CleanSession {
-			c.messageIds.cleanUp()
-		}
+		c.messageIds.cleanUp()
 		if c.options.AutoReconnect {
 			c.setConnected(reconnecting)
 			go c.reconnect()

Diff for: token_test.go

@@ -0,0 +1,14 @@
+package mqtt
+
+import (
+	"testing"
+	"time"
+)
+
+func TestWaitTimeout(t *testing.T) {
+	b := baseToken{}
+
+	if b.WaitTimeout(time.Second) {
+		t.Fatal("Should have failed")
+	}
+}