Alexey Merzlyakov

This is the first attempt to add range sensors support to the Collision Monitor. The range arc `{-field_of_view/2 .. field_of_view/2}` from `sensor_msgs/msg/Range` message is being breaked down into equidistant (by...

Hi! I've also thought about it for this week and for this case would like to vote for the another `nav2-extentions` repository (or `ros-*` or anything you want) for this...

> I would not like to create a nav2-extensions project, that would put the maintainer burden on me for things that might not be as well tested or have assistance...

I've also started the review, but due to amount of changes in this PR and my LP-related and org. activities it still not done yet. Plan to finish it up...

@ryzhikovas, I did retest at OSRF docker from the scratch. Now everything seems is OK: headers are being covering by ~100%. It looks like previous time it was my local...

@ryzhikovas, regarding update to the latest `main` branch: the history should be linear, so you need to rebase your changes onto latest `main` from upstream, if you have some conflicts...

Now I see the same problem for keepout test concerned with Gazebo server crashing at CI side: ``` [ERROR] [gzserver-1]: process has died [pid 3854, exit code 255, cmd 'gzserver...

Update information: I've run `test_keepout_filter` in a built workspace with AWS under same Docker container (as used with CI) locally. Test works fine, so this is the same as for...

I've made rviz visualization of test. From the rviz, looks like robot have to received incorrect initial pose position and rotation in the test. This picture was taken after receiving...

@lucabonamini thank you for the analysis! Confirming this statement: `gzserver` is not being killed after each testcase run, so next testcase running with it will cause incorrect robot spawning position...