Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Receiving rosout messages from rosbag2_recorder when running rosbag2_player #1798

Open
scn-nmsc opened this issue Sep 3, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@scn-nmsc
Copy link

scn-nmsc commented Sep 3, 2024

Description

ros2 bag play /testbag results in "rosbag2_recorder" actively publishing discovery log messages.

Expected Behavior

When starting rosbag2_player then "rosbag2_recorder" should not appear to be subscribing to messages according to /rosout topic.

Actual Behavior

When starting rosbag2_player (ros2 bag play /testbag) then "rosbag2_recorder" appears in the /rosout to be subscribing to topics (e.g. rosbag2_recorder: All requested topics are subscribed. Stopping discovery...)

To Reproduce

** Steps to reproduce the behavior, e.g.

  1. run "ros2 bag play /testbag"
  2. and subscribe to /rosout topic

System (please complete the following information)

  • OS: Ubuntu 24.04
  • ROS 2 Distro: Jazzy
  • Install Method: APT
  • Version: 0.26.4
@scn-nmsc scn-nmsc added the bug Something isn't working label Sep 3, 2024
@MichaelOrlov
Copy link
Contributor

@scn-nmsc The Expected behaviour is unclear

When starting rosbag2_player then "rosbag2_recorder" should not appear to be subscribing to messages according to /rosout topic.

In the form how it is written is impossible to implement in the current design because rosbag2_recorder can't know that messages on the /rosout topic coming from the rosbag2_player

@fujitatomoya
Copy link
Contributor

I am not sure what the problem is with this issue report... can you rephrase the issue header?

Are you saying that ros2 bag play /testbag should not play rosout topic according to the To Reproduce section in the issue header? if that is so, why do you not specify or exclude the topic to play? the same can be don on ros2 bag record as well, so user can have the full control what needs to be recorded and played?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants