44a542391e
This should address issue as described in https://forum.syncthing.net/t/stun-nig-party-with-paused-devices/10942/13 Essentially the model and the connection service goes out of sync in terms of thinking if we are connected or not. Resort to model as being the ultimate source of truth. I can't immediately pin down how this happens, yet some ideas. ConfigSaved happens in separate routine, so it's possbile that we have some sort of device removed yet connection comes in parallel kind of thing. However, in this case the connection exists in the model, and does not exist in the connection service and the only way for the connection to be removed in the connection service is device removal from the config. Given the subject, this might also be related to the device being paused. Also, adds more info to the logs GitHub-Pull-Request: https://github.com/syncthing/syncthing/pull/4533 |
||
|---|---|---|
| .. | ||
| config.go | ||
| connections_test.go | ||
| debug.go | ||
| kcp_dial.go | ||
| kcp_listen.go | ||
| kcp_misc.go | ||
| limiter.go | ||
| relay_dial.go | ||
| relay_listen.go | ||
| service.go | ||
| structs.go | ||
| tcp_dial.go | ||
| tcp_listen.go | ||
| util.go | ||