We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
版本: 0.9.9 运行服务器: Google Cloud 台湾区 n1
运行一段时间后,出现稳定性问题。该问题似乎在上版本也存在,但这个版本又复现了。
Bug reporter: BitPortal
2019-04-26 03:32:49.430 INFO [runtime|xrml_xsystem] height:39320, blockproducer: 61b5932a5a0832b28c7f1fd67261e0c1e93da4239916472ad3aa2deb1193eb02 (5EGpSXhp...)|name:NodeSoleil ==================== stack backtrace: 0: substrate_panic_handler::set::{{closure}}::h3ac648907d84f931 (0x55ba9bb55b0f) 1: rust_panic_with_hook (0x55ba9bd413c8) at src/libstd/panicking.rs:478 2: std::panicking::begin_panic::hd1b275492f3b6bff (0x55ba9b9414a4) 3: chainx_runtime::xexecutive::Executive<System,Block,Context,Payment,AllModules>::execute_block::hef7cedd90dae9beb (0x55ba9b970962) 4: chainx_runtime::api::dispatch::h16e2ba2969aa5372 (0x55ba9b8ba7a2) 5: std::panicking::try::do_call::hc5e87824aef7d012 (0x55ba9b342c61) 6: __rust_maybe_catch_panic (0x55ba9bd46df9) at src/libpanic_unwind/lib.rs:85 7: substrate_executor::native_executor::safe_call::h7e5d22bee70f85d0 (0x55ba9b343372) 8: std::thread::local::LocalKey<T>::with::haf73e46118f70b34 (0x55ba9b342d96) 9: <chainx_executor::Executor as substrate_executor::native_executor::NativeExecutionDispatch>::dispatch::hc882303ccffa3fb4 (0x55ba9b3426bc) 10: std::thread::local::LocalKey<T>::with::h0dd1d2b55861767a (0x55ba9b04b138) 11: substrate_state_machine::StateMachine<H,B,T,O,Exec>::execute_aux::h64f140fd0296b8c1 (0x55ba9af1a2b2) 12: substrate_state_machine::StateMachine<H,B,T,O,Exec>::execute_call_with_native_else_wasm_strategy::hf5f42670a3b53e01 (0x55ba9af9b962) 13: substrate_state_machine::StateMachine<H,B,T,O,Exec>::execute_using_consensus_failure_handler::ha5195f7735f40328 (0x55ba9af77761) 14: <substrate_client::call_executor::LocalCallExecutor<B,E> as substrate_client::call_executor::CallExecutor<Block,substrate_primitives::hasher::blake2::Blake2Hasher>>::call_at_state::h8ae1a6916df3ff99 (0x55ba9b0140b1) 15: substrate_client::client::Client<B,E,Block,RA>::lock_import_and_run::{{closure}}::h38208b2ce9cae960 (0x55ba9b194f5e) 16: <substrate_client::client::Client<B,E,Block,RA> as substrate_consensus_common::block_import::BlockImport<Block>>::import_block::hd74eacc942e5f3af (0x55ba9b1864d1) 17: <substrate_finality_grandpa::import::GrandpaBlockImport<B,E,Block,RA,PRA> as substrate_consensus_common::block_import::BlockImport<Block>>::import_block::h5f29e85a2d8e9910 (0x55ba9b0f46e1) 18: substrate_consensus_common::import_queue::BlockImportWorker<B,V>::import_a_batch_of_blocks::h66a89532c190eb6c (0x55ba9aeccd5d) 19: std::sys_common::backtrace::__rust_begin_short_backtrace::ha2ba196ad89ca1d5 (0x55ba9b2fa2fe) 20: std::panicking::try::do_call::h869436222e77f206 (0x55ba9ac93ffd) 21: __rust_maybe_catch_panic (0x55ba9bd46df9) at src/libpanic_unwind/lib.rs:85 22: core::ops::function::FnOnce::call_once{{vtable.shim}}::h81a8af19346b6d9a (0x55ba9b09bb92) 23: call_once<(),FnOnce<()>> (0x55ba9bd2e7ee) at /rustc/70f130954d6fd36fe3e77f4b5b33e5af50489288/src/liballoc/boxed.rs:704 24: call_once<(),alloc::boxed::Box<FnOnce<()>>> (0x55ba9bd4610f) at /rustc/70f130954d6fd36fe3e77f4b5b33e5af50489288/src/liballoc/boxed.rs:704 start_thread at src/libstd/sys_common/thread.rs:13 thread_start at src/libstd/sys/unix/thread.rs:79 25: start_thread (0x7f90370646da) 26: __clone (0x7f9036b7588e) 27: <unknown> (0x0) Thread 'ImportQueueWorker' panicked at 'All extrinsics should have the correct nonce', runtime/src/xexecutive.rs:183 This is a bug. Please report it at: https://github.com/chainx-org/ChainX
The text was updated successfully, but these errors were encountered:
No branches or pull requests
版本: 0.9.9
运行服务器: Google Cloud 台湾区 n1
运行一段时间后,出现稳定性问题。该问题似乎在上版本也存在,但这个版本又复现了。
Bug reporter: BitPortal
The text was updated successfully, but these errors were encountered: