Dharini Dutia

`test_launch_test_ros_subscriber.launch.py` is failing for fortress+humble

I was not able to reproduce this, is the same test failing every time?

A suggestion was to check if its a flaky test or not by trying `--retest-until-pass N`.

Using debian packages is the preferred option and to be sought out first as it would be beneficial in the long run.

**TD;LR The answer is not keep re-sourcing/re-overlaying in the same terminal.** So this is happening with ROS1 Noetic + ROS2 Humble on Ubuntu 22.04 (Jammy) as well. ``` root@eb1dc6b69d3f:~/bridge_ws# source...

Can you please share your Dockerfiles and source code to reproduce the issue, or preferably try with the official [osrf/docker_images/galactic/ubuntu/focal/ros1-bridge](https://github.com/osrf/docker_images/blob/master/ros/galactic/ubuntu/focal/ros1-bridge/Dockerfile) image?

Looks like the homebrew CI passed!

@oKermorgant Thanks for your contribution! Do you mind refactoring the header a bit based on the suggestions by the workflow run, like one [here](https://build.ros2.org/job/Rpr__sdformat_urdf__ubuntu_jammy_amd64/33/testReport/), it's mostly reformatting, missing spaces, etc.

@oKermorgant regarding the environment variables, Gazebo will look for URIs (path / URL) in the following order: 1. All paths on the `GZ_SIM_RESOURCE_PATH` 2. Current directory 3. Cache ($HOME/.gz) The...

Hi @alexg-k, thanks for sharing the docker image! (Though its a very large file, please consider modifying this [Dockerfile](https://github.com/osrf/docker_images/blob/master/ros/foxy/ubuntu/focal/ros1-bridge/Dockerfile) for faster porting.) I could reproduce your issue. But I noticed...