Skip to content

memesh doctor stays silent about a damaged Codex release record #504

Description

@kevintseng

memesh doctor checks whether a Codex message is stuck because no Codex daemon was running to release it. If one of the stored records it reads is damaged, doctor skips that record and says nothing, so a stuck message can go unreported.

memesh itself always writes these records correctly, so this only happens if the database was changed by something else.

Expected: doctor names any record it could not read, instead of skipping it.

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