-
Notifications
You must be signed in to change notification settings - Fork 163
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
Expose QoS settings for /rosout publisher #581
Comments
While exposing the QoS settings would be great I think the default still needs to be different. Currently it uses See #582 for the proposal. @de-vri-es It would be great if you could give this patch a try and comment if that resolves your issue. |
That does sound like a good idea. I'm not very familiar with compiling on Windows, which is where I witnessed the issue, but I'll try my best to test it. |
Sounds good. Thanks all for the quick action :) |
@dirk-thomas @ivanpauno @de-vri-es anybody working on this? if not, we could take care of this thread. |
AFAIK, nobody is working on this. Usually, people assign themselves when they are working on something (though they might forget 😂). |
Hi, @ivanpauno @fujitatomoya I made a PR for this issue, now only rcl/rmw layer was implemented. As for the rclcpp layer, i have already finished a design draft, which we can discuss later, For now, can you take a quick look for 253 && 722 in your spare time? |
Solved in #722 |
I have noticed that sometimes during node startup, some messages don't arrive at
/rosout
subscribers. I could never replicate this on my own Linux hardware, but I have witnessed it on a Windows PC. Log messages from the first 30 to 100ms would not arrive at a subscriber.I imagine this could be fixed by changing the QoS settings of the publisher. However, I don't believe we have access to the publisher or it's QoS settings at the moment. If it is true that changing the QoS settings could prevent loosing messages during startup (within reason), could these settings be exposed?
Log messages during node startup can be especially interesting, so it's not nice to loose them.
The text was updated successfully, but these errors were encountered: