Closed GuutBoy closed 6 months ago
@GuutBoy Could you try running this in the latest on develop
? This may be fixed there.
@smcclellan I can confirm this is on the latest develop
. I wonder if I may be missing some arguments? Even so, this probably should not result in a panic. I am simply running
ordhook db repair blocks
@GuutBoy how about now?
Still the same
$ ordhook db repair blocks --config-path Ordhook.toml
thread 'main' panicked at 'internal error: entered unreachable code', components/ordhook-cli/src/cli/mod.rs:259:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
I am guessing it is because I need to add options like --blocks
or something.
correct. if you don't know which blocks to repair, you can use the command
$ ordhook service start --config-path Ordhook.toml
the new version should run some integrity checks and auto-repair broken states.
Feel free to re-open this issue with more logs if you're still having some trouble.
To deal with the issue in #258 I attempted to repair blocks using the
ordhook db repair blocks
command. However this only resulted in a main thread panic. See output belowWith the full backtrace: