Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix corrupted databases by using redb 0.13.0 #1513

Merged
merged 1 commit into from
Feb 6, 2023

Conversation

hantuzun
Copy link
Contributor

@hantuzun hantuzun commented Feb 5, 2023

This PR fixes https://github.com/casey/ord/issues/1471 by bringing the fix for cberner/redb#515.

@casey
Copy link
Collaborator

casey commented Feb 6, 2023

Excellent, thank you for identifying the issue, working with @cberner, and opening this PR with the fix! Merging now.

Why did the lifetimes change? Everything compiles and the tests passes, so it's fine, I just don't understand the what caused the change.

@casey casey merged commit fdb1396 into ordinals:master Feb 6, 2023
@cberner
Copy link
Contributor

cberner commented Feb 6, 2023

I changed redb to only accept 'static lifetimes for the keys and values. Those lifetimes have no meaning because all the get(), insert()...etc functions generate their own lifetimes based on &self via the SelfType GAT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot run ord server after a crash due to cberner/redb#515
3 participants