panicked on reorg

[zhiying8710]

network: testnet

[2024-04-02T12:35:21Z INFO  ord::index] 3 block deep reorg detected at height 2584936
[2024-04-02T12:35:21Z INFO  ord::index::reorg] rolling back database after reorg of depth 3 at height 2584936
thread '<unnamed>' panicked at src/index/reorg.rs:66:76:
called `Option::unwrap()` on a `None` value
stack backtrace:
   0:     0x562207680096 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h9cca0343d66d16a8
   1:     0x5622076b0580 - core::fmt::write::h4311bce0ee536615
   2:     0x56220767b85f - std::io::Write::write_fmt::h0685c51539d0a0cd
   3:     0x56220767fe74 - std::sys_common::backtrace::print::h2fb8f70628a241ed
   4:     0x5622076816f7 - std::panicking::default_hook::{{closure}}::h05093fe2e3ef454d
   5:     0x562207681459 - std::panicking::default_hook::h5ac38aa38e0086d2
   6:     0x562207681b88 - std::panicking::rust_panic_with_hook::hed79743dc8b4b969
   7:     0x562207681a29 - std::panicking::begin_panic_handler::{{closure}}::ha437b5d58f431abf
   8:     0x562207680596 - std::sys_common::backtrace::__rust_end_short_backtrace::hd98e82d5b39ec859
   9:     0x5622076817b4 - rust_begin_unwind
  10:     0x562206990035 - core::panicking::panic_fmt::hc69c4d258fe11477
  11:     0x5622069900f3 - core::panicking::panic::h90e84101c01877ef
  12:     0x56220698ff86 - core::option::unwrap_failed::hac39b9b7507453f8
  13:     0x562206f3eb61 - ord::index::reorg::Reorg::handle_reorg::hdc133cab32e10f64
  14:     0x562206d1d721 - ord::index::Index::update::hfe666c71eebb0c0a
  15:     0x562206f04275 - std::sys_common::backtrace::__rust_begin_short_backtrace::h5bdaa74c7c6e42df
  16:     0x562206c0e7a9 - core::ops::function::FnOnce::call_once{{vtable.shim}}::hd30e120ce2c63608
  17:     0x562207686db5 - std::sys::pal::unix::thread::Thread::new::thread_start::h40e6fd3f8ce15a14
  18:     0x7f050afe5ac3 - <unknown>
  19:     0x7f050b077850 - <unknown>
  20:                0x0 - <unknown>

[zhiying8710]

just happend again:

Ord just caught up with the latest block on the testnet, and then a reorg happened. I'm wondering if it's because it just caught up with the latest block on the testnet, and at this point, there are no save_pointers causing this panic?
@casey

[raphjaph]

Yes, that might be the case. There's a PR open that might fix this, I'll have to revive it. ##2365