Skip to content

Appropriately parse messages with unknown block ids #47

Description

@freeman94

Currently, if a message has a valid header and an unsupported block id, we throw it away and continue looking for sync bytes. This has a performance penalty because we now parse out a byte at a time over what was known to be a valid message.

We could read out the remaining bytes in the valid message without parsing, but the proptest failure added in #46 presents a challenge to overcome if we choose to do this.

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