Felix Exner (fexner)
Felix Exner (fexner)
The latest changes introduced braking changes and we require this for building correctly. Changing from master to a specific version will make sure that we won't suddenly not build anymore...
Since the main branch is targeted for ubuntu jammy, where there is no clang-format-10 available anymore, we should raise that to 14, as this is the default clang-format version on...
We currently need 2.9.0 to build against, but this is not yet synced to the main repos. Once this is synced, we can remove the ros2_controllers entry from the not_released.repos...
In the ROS1 driver we could set the payload through ROS. This is still missing.
In certain situations (e.g. driver running in a docker container) it is useful to specify the IP address injected into the script code where the reverse interface is reachable from...
The test scripts depend on ros2_control_test_nodes, which is not released for Foxy (and probably will not, since for galactic+ it is included into ros2_controllers). We could provide our own testing...
The test scripts (for example [this](https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/blob/main/ur_robot_driver/test/integration_test.py) have a weird dependency on `ur_bringup` using https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/blob/24224994fb001b0d30acf6053eedfc27245c74c3/ur_robot_driver/test/integration_test.py#L78 This works as long as you have a source build, but seems like a horrible thing...
I just tried to build a new workspace on ROS foxy using the binary-build method, so only with `ros2_control_demos`, `Universal_Robots_Client_Library`, `Universal_Robots_ROS2_Driver`, `ur_msgs` inside my workspace and it failed. One outcome...
The integration tests require a running robot (or simulation) connected to the ROS machine for functioning correctly. Currently, they are run on each `make test`, however, making the buildfarm builds...