feat(cmd): DB verification with cmd tool#3335
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #3335 +/- ##
==========================================
- Coverage 75.98% 75.80% -0.18%
==========================================
Files 377 384 +7
Lines 34614 35126 +512
==========================================
+ Hits 26301 26627 +326
- Misses 6466 6623 +157
- Partials 1847 1876 +29 ☔ 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:
|
fd6591e to
cd9f31e
Compare
thiagodeev
left a comment
There was a problem hiding this comment.
Hey. Nice work!
I've made a few comments. Some of them are just nitpicks and can be easily ignored, but I believe the rest are relevant.
Unfortunately, due to my lack of knowledge of the state and DB, I couldn't help very much with the verification logic, only with general logic things.
|
This pull request is stale because it has been open 35 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
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>