Keep getting error "plot panicked"
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start at Plot::load in crates/core/src/plot/mod.rs around line 995 and inspect how ./world/plots/p0,0 is deserialized. Reproduce with the supplied error if possible, then trace the invalid enum tag handling. Done should mean the affected plot no longer prevents the server from starting, with a regression test for the loading failure if the existing test structure supports it.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 106
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MCHPR/MCHPRS
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100