Skip to content

Error handling after subscribe #2

@cybrown

Description

@cybrown

When we use a GET command after a SUBSCRIBE command on the same connection, the returned result is an Optional.empty.

The error is not reported, and I had to look far into the stack to find the issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions