Skip to content

Legacy import should error when it fails #24

@unenglishable

Description

@unenglishable

With the current implementation, on a failed import to the legacy db (in level), there is no error message. Because of this, future lookups of legacy data can return NotFoundError: Key not found in database when trying to find an entry that was not successfully imported.

It would be helpful for the error message to show which legacy imports failed and why.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions