-
Notifications
You must be signed in to change notification settings - Fork 222
feat(cmd): DB verification with cmd tool #3335
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report❌ Patch coverage is
❌ Your patch check has failed because the patch coverage (24.32%) is below the target coverage (60.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #3335 +/- ##
==========================================
- Coverage 76.05% 76.04% -0.01%
==========================================
Files 347 349 +2
Lines 32829 32864 +35
==========================================
+ Hits 24967 24992 +25
- Misses 6074 6085 +11
+ Partials 1788 1787 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I don't know if the PR plans to go live like this, but I strongly suggest it gets divided in two:
|
This PR introduces a new cmd tool, which can be used for the DB corruption verification. For now its just an empty command. The new commands will be added in the followup PRs. To use the tool, hit:
juno verify --db-path <path>