-
Notifications
You must be signed in to change notification settings - Fork 30
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
keep record latch message when reset buffer #6
Comments
I don't recall what the current behavior is. Do the latched messages fall out of the recording window? |
I see the code, when flush recording buffer, every message will be drop. |
Is this issue no longer relevant for you? For us it is (not highest prio at the moment though). Would you mind keeping it open 'for the record'? |
@Timple Thank you for caring about this issue, now I use a temporary way be work around, just resend latch message when play bag. |
This issue is also relevant for us :-) |
Related ROS Answers (I believe posted by @arneboe): Is it possible to know if a topic is latched on subscriber side in cpp. |
yep that was me (sorry for the double post btw.). |
Another option would be to drop all connections and re-subscribe to all topics. All the latched topics would be send again. Note: This might result in some message loss in-between bagfiles (we don't care). |
+1. It seems like using the same logic we use here should work. |
You can just use this and it'll keep the first message:
|
Hello, Have any plan keep record latch message?
The text was updated successfully, but these errors were encountered: