Closed mirenz1 closed 2 weeks ago
The cause for this might be architectural. Currently, LEA gets the list of connected peers from the PeerMessagingBroker, whereas the list of peers comes from the PeerManager. The PeerMessagingBroker already published the states of peers into the ResourcesManager, so the PeerManager could grab this information and provide a consolidated list.
This would be a somewhat larger refactoring, though, and it's unclear whether it would actually fix anything, so it makes sense to simply debug this at first, to find out where in the whole application the state starts becoming incorrect.
We changed the way this status is loaded (now via PeerManager.get_peer_state()), so we hope this issue is resolved. Closing for now.
See #277.
Peer connection status is not correctly shown in LEA
see also #7