Skip to content
New issue

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

Keep getting error "plot panicked" #96

Open
Marterido opened this issue Dec 7, 2022 · 3 comments
Open

Keep getting error "plot panicked" #96

Marterido opened this issue Dec 7, 2022 · 3 comments

Comments

@Marterido
Copy link

Hey! I've been getting this error a lot lately and don't know how to fix it. Because of this error i can't get onto my server anymore. Any idea how to fix this?

[2022-12-07 18:40:35][mchprs_core::server][ERROR] plot panicked at 'called `Result::unwrap()` on an `Err` value: error loading plot 0,0

Caused by:
    0: error loading plot save file at ./world/plots/p0,0
    1: plot data deserialization error
    2: tag for enum is not valid, found 101', crates/core/src/plot/mod.rs:995:18
   0: backtrace::capture::Backtrace::new
   1: mchprs_core::server::MinecraftServer::run::{{closure}}
   2: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
             at /rustc/b7bc90fea3b441234a84b49fdafeb75815eebbab/library/alloc/src/boxed.rs:2032:9
      std::panicking::rust_panic_with_hook
             at /rustc/b7bc90fea3b441234a84b49fdafeb75815eebbab/library/std/src/panicking.rs:692:13
   3: std::panicking::begin_panic_handler::{{closure}}
             at /rustc/b7bc90fea3b441234a84b49fdafeb75815eebbab/library/std/src/panicking.rs:579:13
   4: std::sys_common::backtrace::__rust_end_short_backtrace
             at /rustc/b7bc90fea3b441234a84b49fdafeb75815eebbab/library/std/src/sys_common/backtrace.rs:137:18
   5: rust_begin_unwind
             at /rustc/b7bc90fea3b441234a84b49fdafeb75815eebbab/library/std/src/panicking.rs:575:5
   6: core::panicking::panic_fmt
             at /rustc/b7bc90fea3b441234a84b49fdafeb75815eebbab/library/core/src/panicking.rs:65:14
   7: core::result::unwrap_failed
             at /rustc/b7bc90fea3b441234a84b49fdafeb75815eebbab/library/core/src/result.rs:1791:5
   8: mchprs_core::plot::Plot::load
   9: std::sys_common::backtrace::__rust_begin_short_backtrace
  10: core::ops::function::FnOnce::call_once{{vtable.shim}}
  11: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/b7bc90fea3b441234a84b49fdafeb75815eebbab/library/alloc/src/boxed.rs:2000:9
      <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/b7bc90fea3b441234a84b49fdafeb75815eebbab/library/alloc/src/boxed.rs:2000:9
      std::sys::unix::thread::Thread::new::thread_start
             at /rustc/b7bc90fea3b441234a84b49fdafeb75815eebbab/library/std/src/sys/unix/thread.rs:108:17
  12: _pthread_from_mach_thread_np
@AL1L
Copy link
Contributor

AL1L commented Dec 7, 2022

Quickest way would be to delete plot 0 0, looks like it might be corrupted. Send the plot file here, maybe we can recover it.

@Marterido
Copy link
Author

Ah that sucks, was already worried it was gonna be something like that. Here's the zip file of just that one plot:
p0,0.zip

@Marterido
Copy link
Author

Any idea if recovery is possible? I would love to hear about it

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

No branches or pull requests

2 participants