Closed deng02 closed 7 years ago
Hi,
you are right, there is a bug. But the new fix leads also to a deadlock. I will try to fix it.
regards
Hi,
I fixed this issue. Can you try it out, please.
regards
The issue appears to have been fixed based on my initial testing of the latest master branch. Thanks! I consider this solved. If possible can we get the master branch tagged or have a merge into indigo-devel so we can start testing the fixes in our larger test bed?
I merged the changes into indigo-devel.
@atiderko Happy New Year! This bug is fixed and can be closed. Would it be possible to get a release?
Happy New Year!
there are some other small bugs in node manager. I will fix it and then create a release.
Hi,
So we're attempting to setup a hub toplogy using the new listen_mcast and send_mcast settings. Our hub clients have listen_mcast set to True and send_mcast set to False. The hub itself has listen_mcast and send_mcast set to True.
When we run in this type of configuration our clients can see the hub just fine (and not each other which is great!) but unfortunately the hub can't see the clients since the client never sends out anything as part of its heartbeat. We actually need them to see each other as there is topics and services that must be synchronized between the two.
A simple change that would allow a client to see a hub and vice versa would be to modify the send_heartbeat() to send the master discovery current state to each address in self._address if listen_mcast is True but send_mcast is False:
I'm not sure what you think of this.
Thanks.