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.

Sign up for GitHub

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

Jump to bottom

[5.0] clear the DB dirty bit if pinnable_mapped_file fails to fully start #2132

Merged
merged 1 commit into from
Jan 24, 2024
Merged

[5.0] clear the DB dirty bit if pinnable_mapped_file fails to fully start #2132

merged 1 commit into from
Jan 24, 2024

Conversation

spoonincode
Copy link
Member

Bumps the chainbase submodule to chainbase's leap-5.0 branch head with AntelopeIO/chainbase#38 fixing #2086

@spoonincode spoonincode linked an issue Jan 24, 2024 that may be closed by this pull request
When mapped_private doesn't work, database is left dirty #2086
Closed
@spoonincode spoonincode merged commit 2c006cd into release/5.0 Jan 24, 2024
29 checks passed
@spoonincode spoonincode deleted the reset_dirty_mapped_private_50 branch January 24, 2024 20:38
@spoonincode spoonincode mentioned this pull request Jan 24, 2024
Merged
@ericpassmore
Copy link
Contributor

Note:start
group: STABILITY
category: BUG
summary: Revs chainbase version to include a bug fix. Leap will now start up cleanly in non-mapped_private mode after failing to startup in mapped_private mode due to lack of swap and/or physical memory.
Note:end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@heifner heifner heifner approved these changes

@greg7mdp greg7mdp greg7mdp approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

When mapped_private doesn't work, database is left dirty
4 participants
@spoonincode @ericpassmore @greg7mdp @heifner