Skip to content

No value present when receiveSyncMessage twice with the same payload #8

Description

@eneroth

Occurs for both identical and equal payloads.

To reproduce this, receive the same bytes sequence of bytes twice. A NoSuchElementException is raised from Optional somewhere in receiveSyncMessage. It seems that every message received after this occurs will be met with the same exception, new or not.

generateSyncMessage seems to exhibit the same behavior after raising the exception in receiveSyncMessage, suggesting that there might be something stateful breaking after the exception occurs the first time.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions