The add_analyzer fails to clean up...sometimes about diagnostics HOT 4 OPEN

Investigating the bond mechanisms in bondpy.

from diagnostics.

Issue in bond_core#14

from diagnostics.

Investigating what nodelets do...they have the same problems even though it's cpp. However the loaders there make a service call to the nodelet manager just before breaking the bond. i.e. they are not relying on the 1) the bond informing the other end or 2) the bond breaking to make sure things work.

• unloadNodelet just before bond_break@shutdown
• service call \in unloadNodelet

Could do the same here.

from diagnostics.

We've encountered some similar issues when using the add_analyzers service, and the most common case that I've seen is the bondcpp subscriber dropping messages and prematurely dropping the entire add_analyzers node.

All of the add_analyzers nodes are connecting to the same subscriber, and if they send all of their messages at the same time, it can temporarily overwhelm the bond's subscriber queue. the subscriber queue size is 30, and I've seen this happen with about a dozen add_analyzers nodes running (it looks like the bond publishers are sending at 2Hz, but the aggregator queue is only serviced at 1Hz).

I'm working on a patch that moves each bond to its own topic to alleviate this.

from diagnostics.