Paulo Neves
Paulo Neves
It is 2022 and it is still not fixed. A privacy feature no less.
It seems this can happen without incorrect library usage if there is a reconnection. Specifically, I try to call Disconnect() when behind the scenes a reconnection happened. ``` WARNING: DATA...
Ok i had a look that the code and it is very tricky. We have a mutex(connMu) protecting concurrent writing `c.commsStopped = make(chan struct{})` but we do nothing about reading...
Thank you for your fast and thorough answer > This is not ideal but given how rare this set of circumstances is may be the best option? We will try...
The error is always reproducible if running `go test -race -run Test_autoreconnect -v`
After understanding the code better and specifically the Disconnect() method I find that just removing the following line fixes the issue without any real adverse effects: ``` case
@MattBrittan Thank you. Honestly, I have a [big refactoring and fat-cutting patch privately](https://github.com/ptsneves/paho.mqtt.golang/tree/dev-wip), but this issue does not seem solvable without ugly synchronization primitives for the commsStopped channel.
Looks good. A better commit message explaining the why would make it easier to understand why it should be merged :)
@shrpne it is quite simple. Each element in svg can have an id, and as a standalone svg it is up to the svg provider to guarantee it is unique...
@lathiat We are also being hit by this problem and verified the problem is solved by this PR. The test your are looking for is one which demonstrates the problem...