Michael Orlov

@M201871109 As a workaround I can suggest to try calling `writer_->close()` before `writer.reset()`

@M201871109 As regards > it can close correctly in project A, but can not in project B and no metadata.yaml created. When you mentioned different projects what did you mean...

- Closing as fixed in the https://github.com/ros2/rosbag2/pull/1653 - Note. We do have a unit test to make sure that `rosbag2_cpp::Writer` can be opened and closed multiple times https://github.com/ros2/rosbag2/blob/rolling/rosbag2_tests/test/rosbag2_tests/test_rosbag2_cpp_api.cpp#L44-L116 - I...

@roncapat Any ideas why `ros2 param set /bag_player uri "/path/to/file2"` doesn't work as expected?

@KenYN @roncapat I think we will close this issue as unsupported by design. @roncapat BTW as regards > (Assuming we can get notified by something that a parameter has changed)....

- Closing this issue as functionality is currently unsupported by design.

- Closing as fixed in the #345

@amacneil Yes we have the reason to not do this for the sake to have deterministic replay. This is duplicate of the https://github.com/ros2/rosbag2/pull/1051 please see my detailed explanation in https://github.com/ros2/rosbag2/pull/1051#pullrequestreview-1059614100

If users want something it doesn't means that we should jump in and implement what they want without considering other cases and drawbacks. My main point not in the case...

@jhurliman Though the way how it's organized in DDS and ROS2 is that publisher has cache with N number of messages when transient local durability is used and when new...