Skip to content

handle_call crashes in "catch-all" case #22

Description

@ThomasArts

Most likely the message format has changed. At the moment, the message handled in handle_call of leveled_bookie could very well be the atom destroy.

https://github.com/martinsumner/leveled/blob/da06ef133c1d73255434b9518b469c3d301a0b56/src/leveled_bookie.erl#L1425

The catch all case expects it to be a tuple, though.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions