Skip to content

[messenger] log ConsumeMessagesCommand informational notices to stdout instead of stderr #42327

@maryo

Description

@maryo

Not sure if it's a bug, a feature request or just a question. Probably something in between. Why does ConsumeMessagesCommand use stderr instead of stdout for messages like Consuming messages from transport... introduced in #29303? I know i can disable the messages entirely using -q. Wouldn't stdout be more appropriate? Thank you.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions