Conversation
|
At first sight it lok goot (thanks a lot). I will find some time to double check and I will merge it soon. |
|
This would be much needed addition for real-time monitoring. Any progress here? |
|
Hey there, I was testing this PR with my PR for nav2. Without this PR, I had a few errors with reloading trees crashing Groot, as described here. The only thing that is missing is using a different xml, like in this scenario:
(all while the same Groot Monitor is active/open and connected) |
|
Hi @gramss Sorry, there isn't much I can contribute here :( |
|
sorry for ignoring this so long. Thanks for the contribution and the patience. Merged manually because of the conflict. |
* Add missing err:out_of_range code-sections + intent fixes * Revert "Add missing err:out_of_range code-sections + intent fixes" This reverts commit fa8a75b. * indentation fixes * indentation fixes - again * get node status out of try/catch for compiler * main thing: move rest of uid-based logic in try/catch for reload
I have been working with Groot and ROS Navigation2 (modified and publishing ZMQ logger) and had a problem with the monitoring view.
crash reproduction procedure
problem
It tries to find nodes matching to the UIDs in flatbuffer but it needs to know the new tree
fixed strategy