-
Notifications
You must be signed in to change notification settings - Fork 195
Stop flooding the terminal by default with all matches, switch to debug if desired #364
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: ros2
Are you sure you want to change the base?
Conversation
This monitor was not modified in this PR. I'll rebase to see if that helps. |
ed3377a
to
c0a8297
Compare
Ping @ct2034 Any objections here? |
Or can this at least get in before Kilted? 🙂 |
@@ -119,7 +119,7 @@ class GenericAnalyzerBase : public Analyzer | |||
|
|||
has_initialized_ = true; | |||
|
|||
RCLCPP_INFO( | |||
RCLCPP_DEBUG( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we please keep those messages that are not triggered per match on info
Hey @MCFurry @Timple |
…e initial log of the function
Sorry it took a while! |
Based on what we discussed above, that I am happy to change the level in the In any case, I think this would also be a good use for RCLCPP_DEBUG_THROTTLE. What do you think? |
The issue is that there a loop around all parameters: for (const auto & param : parameters) { Every analyzer added prints information about all other analyzers as well. Since we have a lot of analyzers, adding only 1 causes a massive print flood. |
@ct2034 if you like things to be verbose, do you have any ideas how to get around printing always all parameters? |
We noticed that when extending a ROS system with many analyzers, the terminal during startup is flooded with all the analyzer matches.
I reckon these can be debug logs that one can enable when desired.
(Example in the tests, since these require these stdout logs)