Skip to content

Expose QoS settings for /rosout publisher #581

@de-vri-es

Description

@de-vri-es

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions