Thread 'main' panicked at 'Must always set if there is no logical error

Support Incentivized Testnet
, ,
1

Hello, compiling Sep-21 on AMD 5950x, leading to node bin and process not starting at all, see error below. Fedora 37, clang version 15.0.7 (Fedora 15.0.7-2.fc37), cargo 1.73.0-nightly (1b1555676 2023-07-18)

2023-09-22 08:32:41 Subspace
2023-09-22 08:32:41 ✌️  version 0.1.0-c9546e94002
2023-09-22 08:32:41 ❤️  by Subspace Labs <https://subspace.network>, 2021-2023
2023-09-22 08:32:41 📋 Chain specification: Subspace Gemini 3f
2023-09-22 08:32:41 🏷  Node name: ...
2023-09-22 08:32:41 👤 Role: AUTHORITY
2023-09-22 08:32:41 💾 Database: ParityDb at /sub/data/node/sub-33344/chains/subspace_gemini_3f/paritydb/full
2023-09-22 08:32:41 ⛓  Native runtime: subspace-3 (subspace-0.tx0.au0)
2023-09-22 08:32:45 [Consensus] DSN instance configured. allow_non_global_addresses_in_dht=false peer_id=... protocol_version=/subspace/92e91e657747c41eeabed5129ff51689d2e935b9f6abfbd5dfcb2e1d0d035095
2023-09-22 08:32:45 [Consensus] Subspace networking initialized: Node ID is ...
2023-09-22 08:32:45 [Consensus] DSN listening on /ip4/127.0.0.1/tcp/33345/p2p/...
2023-09-22 08:32:45 [Consensus] DSN listening on /ip4/192.168.1.120/tcp/33345/p2p/...
2023-09-22 08:32:45 [Consensus] 🏷  Local node identity is: ...

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

Version: 0.1.0-c9546e94002

   0: sp_panic_handler::set::{{closure}}
   1: std::panicking::rust_panic_with_hook
   2: std::panicking::begin_panic_handler::{{closure}}
   3: std::sys_common::backtrace::__rust_end_short_backtrace
   4: rust_begin_unwind
   5: core::panicking::panic_fmt
   6: core::option::expect_failed
   7: subspace_service::new_full::{{closure}}
   8: subspace_node::main::{{closure}}::{{closure}}
   9: sc_cli::runner::Runner<C>::run_node_until_exit
  10: subspace_node::main
  11: std::sys_common::backtrace::__rust_begin_short_backtrace
  12: std::rt::lang_start::{{closure}}
  13: main
  14: __libc_start_call_main
  15: __libc_start_main@GLIBC_2.2.5
  16: _start


Thread 'main' panicked at 'Must always set if there is no logical error; qed', /home/srv_subspace/subspace/crates/sc-consensus-subspace/src/archiver.rs:530

This is a bug. Please report it at:

        https://forum.subspace.network

2023-09-22 08:32:45 [Consensus] Last archived block 539434
2023-09-22 08:32:45 [Consensus] Archiving already produced blocks 539435..=539434
1 Like
2

Same process and machine to compile 13-2 works.

3

This is an interesting edge-case, will be fixed in the next snapshot with Gemini 3f backport: Fix last archived segment search by nazar-pc · Pull Request #1998 · subspace/subspace · GitHub

Thanks for reporting!

4

Fixed in latest release: Release gemini-3f-2023-sep-24 · subspace/subspace · GitHub
UPD: Release gemini-3f-2023-sep-25 · subspace/subspace · GitHub has more complete fix.

5

That issue went away, thanks.

6

Just got this error. This happend after I restarted the node. Latest gemini 3f release…

7

Screenshot_6
Screenshot_61723×896 74.9 KB

8

As mentioned above the issue was resolved in newer releases.