-
Notifications
You must be signed in to change notification settings - Fork 2
Centralize vision_opencv repository #13
Comments
Thanks @testkit for bringing it up! We discussed it internally a few weeks back and concluded that it should be centralized on https://github.com/ros-perception/vision_opencv as the ROS 2 fork was only temporary.
I started the work of rebasing our changes of
I opened ros-perception#219 with the Once that is merged, we can modify the ROS 2 CI to use the ros2 branch from https://github.com/ros-perception/vision_opencv and just skip the packages that we currently dont use and that are failings tests / having compiler warnings |
@mikaelarguedas, that's great to have this issue considered and the solution is on the way already! |
@mikaelarguedas thanks for your quick support, regarding the test of conversions.py you mentioned
Generally, it contains 4 test cases in it and it takes relatively long time than the other to finish, because it's normal with my trial, could u please give your error log for more details ? thanks ! |
@gaoethan below the console output of the test.
Build warnings:
|
PRs to migrate ROS2 CI to use the https://github.com/ros-perception/vision_opencv repository instead of the ros2 fork: @testkit @gaoethan please speak up if there is any reason to hold this, otherwise I'll go ahead and merge these tomorrow |
@mikaelarguedas thanks for your detail. I create an extra issue ros-perception#221 to track and fix the warning and test failure for you to avoid messy topic here, next I'll investigate and fix it there accordingly. |
When do ROS2 cv_bridge porting, the question about where to host it has been raised and discussed at #12, the final decision is to manage the code in https://github.com/ros-perception/vision_opencv ros2 branch.
Sorry to bring this question to the table again, since we run into a conflict issue when try to add cv_bridge to coming bouncy release. In vision_opencv, there are two key packages, cv_bridge and image_geometry, but they are maintained in ros-perception/vision_opencv and ros2/vision_opencv respectively, which brings difficulties to add these two packages into bloom release system.
For coming bouncy release, we'll copy ROS2 cv_bridge implementation to this project, but it's not an idea way to maintain the code in both repositories moving forward.
There are two options to get it resolved, I list them as below with the order of my preference, pls. comment.
@dirk-thomas @clalancette @gaoethan @mikaelarguedas @vrabaud.
The text was updated successfully, but these errors were encountered: