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.

Sign up for GitHub

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

Jump to bottom

rosbag filter removes latching from topics #685

Closed
tbleher opened this issue Oct 14, 2015 · 2 comments
Closed

rosbag filter removes latching from topics #685

tbleher opened this issue Oct 14, 2015 · 2 comments

Comments

@tbleher
Copy link

tbleher commented Oct 14, 2015

It seems that "rosbag filter" removes the latching=1 flag from filtered topics.
I ran

rosbag filter in.bag out.bag 'topic == "topic1" or topic == "topic2" or topic == "topic3"'

Of the three topics, two were latched in the original file, but none in the resulting file.

This may be a similar issue to #679.
@fishcu fishcu mentioned this issue May 8, 2017
Closed
ddimarco added a commit to ddimarco/ros_comm that referenced this issue Apr 22, 2018
@ddimarco
keep connection header information in rosbag operations (ros#679, ros…
14a504a 
…#685)

* add parameter to return/write connection header to read/write method

* update rosbag operations to use it
mikepurvis pushed a commit that referenced this issue Apr 24, 2018
@ddimarco @mikepurvis
keep connection header information in rosbag operations (#679, #685)
51d3842 
* add parameter to return/write connection header to read/write method

* update rosbag operations to use it
mikepurvis pushed a commit that referenced this issue Apr 24, 2018
@ddimarco @mikepurvis
Keep connection header info in rosbag filter/compress (#1372)
752cf1f 
Fixes #679 and #685.
@sloretz sloretz mentioned this issue Feb 25, 2019
Closed
@peci1
Copy link
Contributor

peci1 commented Nov 7, 2022

Fixed by #1372 and #1473.

@peci1
Copy link
Contributor

peci1 commented Feb 14, 2023

@sloretz @mjcarroll This issue should be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tbleher @peci1 @mjcarroll