is this project still alive?

Commencez par reproduire ./target/release/codechain -c solo avec la toolchain Rust indiquée et examinez les points d’entrée Scheme::initialize_state, load_from et ChainType::scheme de la backtrace. Suivez l’appel merkle_trie::TrieDBMut::insert jusqu’à linked_hash_map-0.5.1/src/lib.rs:174 ; le travail est terminé lorsque la chaîne solo démarre sans ce panic et que la régression est couverte par un test approprié.

➜  codechain git:(master) ✗ rustc --version
rustc 1.56.0-nightly (2f662b140 2021-08-29)

➜  codechain git:(master) ✗ ./target/release/codechain -c solo

====================

stack backtrace:
   0:     0x5571d220df0d - backtrace::backtrace::trace::hec70945fe4dc07ee
   1:     0x5571d2843fd3 - panic_hook::panic_message::h54d28d915ad1fe54
   2:     0x5571d2843dc1 - core::ops::function::Fn::call::h224889e85e5b3fb6
   3:     0x5571d296071e - std::panicking::rust_panic_with_hook::hde97eb7782db5504
                        at library/std/src/panicking.rs:628
   4:     0x5571d2981785 - std::panicking::begin_panic_handler::{{closure}}::h531b374cb1cba3c4
                        at library/std/src/panicking.rs:519
   5:     0x5571d2981725 - std::sys_common::backtrace::__rust_end_short_backtrace::h170e7849f1857b98
                        at library/std/src/sys_common/backtrace.rs:141
   6:     0x5571d29816e1 - rust_begin_unwind
                        at library/std/src/panicking.rs:517
   7:     0x5571d20c61cf - core::panicking::panic_fmt::hcf5f6d96e1dd7099
                        at library/core/src/panicking.rs:101
   8:     0x5571d20c632b - core::panicking::panic::hd695e3b1d0dd4ef4
                        at library/core/src/panicking.rs:50
   9:     0x5571d283235f - lru_cache::LruCache<K,V,S>::insert::h5f5435251edb6248
  10:     0x5571d282ebdb - merkle_trie::triedbmut::TrieDBMut::insert_aux::h8821b7cd02f9895d
  11:     0x5571d282fe3e - <merkle_trie::triedbmut::TrieDBMut as merkle_trie::TrieMut>::insert::hf9fa8b71628ee353
  12:     0x5571d253eafb - codechain_core::scheme::scheme::Scheme::initialize_state::h93bff9241ef51d9b
  13:     0x5571d254725a - codechain_core::scheme::scheme::load_from::h00994b96ef256632
  14:     0x5571d2541f4f - codechain_core::scheme::scheme::Scheme::load::h3fee5f5b13ff4972
  15:     0x5571d22b6a2a - codechain::config::chain_type::ChainType::scheme::h78eed6fbdbbcb49f
  16:     0x5571d242025e - codechain::run_node::run_node::h03dc46dd431371dc
  17:     0x5571d21f5a3b - codechain::main::h8206c64ec4be3df6
  18:     0x5571d22a5582 - std::sys_common::backtrace::__rust_begin_short_backtrace::h7efafcf553e0e9bd
  19:     0x5571d21f5eb9 - main
  20:     0x7fe3fb6b90b2 - __libc_start_main
  21:     0x5571d21c6b6d - _start
  22:                0x0 - <unknown>

Thread 'main' panicked at 'attempted to leave type `linked_hash_map::Node<primitives::H256, std::vec::Vec<u8>>` uninitialized, which is invalid', /home/bifrost/.cargo/registry/src/github.com-1ecc6299db9ec823/linked-hash-map-0.5.1/src/lib.rs:174

This is a bug. Please report it at:

    https://github.com/CodeChain-io/codechain/issues/new