IntersectMBO / IntersectMBO/lsm-tree

[FEATURE] Invert `ErrSnapshotCorrupted` and action registry errors.

Open
#646 1 comment 0 reactions 0 assignees View on GitHub
enhancement lsm-tree priority: low
Dominant language
Haskell
Stars
53
Forks
17
Avg merge
2d 3h
Merged PRs (30d)
4

Description

> @jorisdral [wrote](https://github.com/IntersectMBO/lsm-tree/pull/637#discussion_r2011668477_
):
> Currently, the user would see an `AbortActionRegistryError` or `CommitActionRegistryError` that contains an `ErrSnapshotCorrupted`.
> I think the nicer thing would be if we flip this: the user gets `ErrSnapshotCorrupted` containing a `FileCorruptedError`/`AbortActionRegistryError`/`CommitActionRegistryError`

> @wenkokke wrote:
> It's entirely non-obvious to me how to decide which of the various exceptions under an action registry error should take precedence, e.g., what do you do if there's two file corrupted errors?

> @jorisdral wrote:
> Probably in chronological order

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.