feat(cmd): DB verification with cmd tool#3335
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #3335 +/- ##
==========================================
- Coverage 74.02% 74.01% -0.01%
==========================================
Files 381 386 +5
Lines 40673 40974 +301
==========================================
+ Hits 30108 30328 +220
- Misses 8780 8841 +61
- Partials 1785 1805 +20 ☔ 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. |
1bb79e5 to
b7a8e79
Compare
This PR introduces a new cmd tool, which can be used for the DB corruption verification on the Merkle Trie side. For now its just an empty command. To use the tool, hit:
juno verify --db-path <path>