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

Kagome db-editor update #1552

Merged
merged 10 commits into from
Apr 10, 2023
Merged

Kagome db-editor update #1552

merged 10 commits into from
Apr 10, 2023

Conversation

igor-egorov
Copy link
Contributor

Referenced issues

Resolves #1300

Description of the Change

Fix kagome pruner to make it work again.
Perform pruning in aggressive way where applicable.
Streamline help messages.

Usage Examples or Tests

kagome --help
kagome db-editor
kagome db-editor path/to/polkadot-node/db

Igor Egorov added 3 commits March 31, 2023 09:57
Signed-off-by: Igor Egorov <igor@soramitsu.co.jp>
Signed-off-by: Igor Egorov <igor@soramitsu.co.jp>
Signed-off-by: Igor Egorov <igor@soramitsu.co.jp>
@igor-egorov igor-egorov requested review from kamilsa and turuslan March 31, 2023 08:24
Igor Egorov added 2 commits March 31, 2023 11:57
@igor-egorov igor-egorov enabled auto-merge (squash) March 31, 2023 08:58
@igor-egorov igor-egorov requested a review from turuslan March 31, 2023 08:58
Copy link
Contributor

@kamilsa kamilsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Running db-editor on existing database gave this error:

23.04.10 07:05:59.144832  kagome           Error     AddressPublisher  publishOwnAddress failed: entry not found in database

@igor-egorov igor-egorov merged commit 3aa1148 into master Apr 10, 2023
@igor-egorov igor-egorov deleted the feature/db-editor-update branch April 10, 2023 14:24
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.

Aggressive pruning (with block body removal)
3 participants