Christopher Thompson

@rinjingu I encountered this issue when working on https://github.com/sr99622/libonvif/pull/116 and other changes. After connecting to the camera you have to first get the camera's information and profile: ``` initializeSession(onvif_session_); getActiveNetworkInterfaces(onvif_session_);...

I had the same thought as I was writing up the response. I can add that as part of the `move` commands in my current PR so they get integrated...

Added the `profileCheck` to https://github.com/sr99622/libonvif/pull/119

> @pele1410, all pull requests must be targeted towards the `main` development branch. Once merged into `main`, it is possible to backport to @jazzy, but it must be in `main`...

> @pele1410 this PR is simple enough and I understand it well, its OK to cherry pick this to `main` and as long as CI passes, I'm OK with it....

Doesn't look like they were. I've asked the rclcpp guys in the PR if it can be backported.

https://github.com/ros2/rclcpp/pull/2742#issuecomment-3049289730 Doesn't look like it's going to be backported. Wondering what our options are here. * On the Jazzy branch, can you tolerate an EXPECT_FAIL on that 1 test case?...

While it pains me to do so; I'm going to go for option 1. I've moved the changes into my own codebase already.

My current workaround is to just compile the `onvif-util` directory with this colcon command ``` colcon build --packages-skip-regex="(?=.*onvif.*)(?!onvif-util)" ``` (Simplified from my actual command)

Actually, this won't really work for me. I need the `libonvif` as a .so I can link against in my application and not as a static lib in `onvif-util`.