Info -> Debug

[vatanaksoytezer]

Revert to original log levels of some functions that was changed in https://github.com/ros-planning/moveit2/pull/598/files#diff-25706feb6b355123a5ae63dfa987a1cdd5754087392e9623960ed74a31b56d75R59.

[codecov]

Codecov Report

Merging #692 (ff87793) into main (fc3909e) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #692   +/-   ##
=======================================
  Coverage   54.16%   54.16%           
=======================================
  Files         192      192           
  Lines       20180    20180           
=======================================
  Hits        10929    10929           
  Misses       9251     9251           

Impacted Files	Coverage Δ
...ics_plugin_loader/src/kinematics_plugin_loader.cpp	68.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fc3909e...ff87793. Read the comment docs.

[nbbrooks]

Should we hold off merging this in until we have fix for the different expected kinematics namespace this revealed?

[vatanaksoytezer]

Should we hold off merging this in until we have fix for the different expected kinematics namespace this revealed?

That's a good question: Maybe @JafarAbdi or @henningkayser can chime in?

[v4hn]

Should we hold off merging this in until we have fix for the different expected kinematics namespace this revealed?

The logs are not gone in this patch, so I don't see how the changed log-level does not reveal something anymore?
I expect you can configure the log-levels in ROS2 similarly to ROS's ROSCONSOLE_CONFIG_FILE? If involved developers do not use this approach I would say they should set it up in their workflows to avoid spamming logs for everyone.

[tylerjw]

I expect you can configure the log-levels in ROS2 similarly to ROS's ROSCONSOLE_CONFIG_FILE?

@v4hn last time I tried this was not yet a working feature in ROS 2.

[nbbrooks]

I expect you can configure the log-levels in ROS2 similarly to ROS's ROSCONSOLE_CONFIG_FILE?

@v4hn last time I tried this was not yet a working feature in ROS 2.

Yeah I also don't think this is implemented yet. We can always change it back for debugging, I just think if we push this in it will be easy to ignore the loading issue (I'm unclear on how much of an issue the loading failure is though)

[v4hn]

Excuse me? 😖

It seems it's still only supported to set the global log level on startup, but not the level of individual namespaces.
I really shouldn't be surprised about this, but I still am. MoveIt uses this feature extensively, so we (should) have a strong interest in implementing support for it upstream!