Skip to content
This repository has been archived by the owner on Jul 23, 2019. It is now read-only.

panic at index out of bounds #171

Open
flappyBug opened this issue Jan 18, 2019 · 1 comment · May be fixed by #172
Open

panic at index out of bounds #171

flappyBug opened this issue Jan 18, 2019 · 1 comment · May be fixed by #172

Comments

@flappyBug
Copy link

How to reproduce?

build & run RUST_BACKTRACE=1 XRAY_SRC_PATH=. script/xray . , open xray_ui/lib/app.js with the editor, then panic occurs.

thread 'main' panicked at 'index out of bounds: the len is 29 but the index is 29', libcore/slice/mod.rs:2460:10
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: rust_begin_unwind
   7: core::panicking::panic_fmt
   8: core::panicking::panic_bounds_check
   9: <xray_core::buffer_view::BufferView as xray_core::window::View>::render
  10: <xray_core::window::WindowUpdateStream as futures::stream::Stream>::poll
  11: <futures::stream::map::Map<S, F> as futures::stream::Stream>::poll
  12: <futures::sink::send_all::SendAll<T, U> as futures::future::Future>::poll
  13: <futures::future::chain::Chain<A, B, C>>::poll
  14: futures::task_impl::std::set
  15: <futures::task_impl::Spawn<T>>::poll_future_notify
  16: tokio::executor::current_thread::CurrentRunner::set_spawn
  17: <tokio::executor::current_thread::scheduler::Scheduler<U>>::tick
  18: <scoped_tls::ScopedKey<T>>::set
  19: <std::thread::local::LocalKey<T>>::with
  20: <std::thread::local::LocalKey<T>>::with
  21: <std::thread::local::LocalKey<T>>::with
  22: tokio_core::reactor::Core::poll
  23: xray_server::main
  24: std::rt::lang_start::{{closure}}
  25: std::panicking::try::do_call
  26: __rust_maybe_catch_panic
  27: std::rt::lang_start_internal
  28: main
@flappyBug flappyBug linked a pull request Jan 18, 2019 that will close this issue
@chambaw

This comment has been minimized.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
@flappyBug @chambaw and others