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

Expose QoS settings for /rosout publisher #581

Closed
de-vri-es opened this issue Feb 26, 2020 · 8 comments
Closed

Expose QoS settings for /rosout publisher #581

de-vri-es opened this issue Feb 26, 2020 · 8 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@de-vri-es
Copy link

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.

@dirk-thomas dirk-thomas added bug Something isn't working enhancement New feature or request labels Feb 26, 2020
@dirk-thomas
Copy link
Member

While exposing the QoS settings would be great I think the default still needs to be different. Currently it uses rmw_qos_profile_default but something like rmw_qos_profile_parameters which changes the depth to 1000 and the duratbility to transient local would be more appropriate.

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.

@de-vri-es
Copy link
Author

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.

@ivanpauno ivanpauno removed the bug Something isn't working label Mar 4, 2020
@ivanpauno
Copy link
Member

Deleted the bug label after #582 and #587, the defaults qos are now nicer.
I will left this open, as exposing the qos would still be an improvement.

@de-vri-es
Copy link
Author

Sounds good. Thanks all for the quick action :)

@dirk-thomas dirk-thomas added the help wanted Extra attention is needed label Mar 4, 2020
@fujitatomoya
Copy link
Collaborator

@dirk-thomas @ivanpauno @de-vri-es
CC: @Barry-Xu-2018

anybody working on this? if not, we could take care of this thread.

@ivanpauno
Copy link
Member

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 😂).
We don't usually address issues marked as help wanted. Of course, PRs targeting a help wanted issue are more than welcomed.

@Ada-King
Copy link
Contributor

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?

@ivanpauno
Copy link
Member

Solved in #722

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants