Plume/Plume
9
18
Fork 24
Code Issues 177 Pull requests 8 Releases 8 Wiki Activity

Upgrading from 0.4.0 to 0.5.0 results in rust panic #822

New issue
Closed
opened 2020-09-18 13:21:48 +00:00 by iamdoubz · 3 comments
iamdoubz commented 2020-09-18 13:21:48 +00:00
Copy link

Bash error:

plume@hammurabi:~/Plume$ RUST_BACKTRACE=full /home/plume/.cargo/bin/plume
Configuration read from /home/plume/Plume/.env
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: IndexCreationError', src/main.rs:126:18
stack backtrace:
   0:  0x106e3d1 - backtrace::backtrace::libunwind::trace::h85c30131a0dec24e
                       at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
   1:  0x106e3d1 - backtrace::backtrace::trace_unsynchronized::h921997e0546f34ae
                       at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
   2:  0x106e3d1 - std::sys_common::backtrace::_print_fmt::h21982e53f592a106
                       at src/libstd/sys_common/backtrace.rs:77
   3:  0x106e3d1 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h69c6e5980f3aaa11
                       at src/libstd/sys_common/backtrace.rs:59
   4:  0x109243c - core::fmt::write::h0762c8ebcff34b38
                       at src/libcore/fmt/mod.rs:1057
   5:  0x106790c - std::io::Write::write_fmt::h1371e7e0e42f565d
                       at src/libstd/io/mod.rs:1426
   6:  0x1070e6e - std::sys_common::backtrace::_print::h30f48ac6a25f64b4
                       at src/libstd/sys_common/backtrace.rs:62
   7:  0x1070e6e - std::sys_common::backtrace::print::h102780d90ef5dd2b
                       at src/libstd/sys_common/backtrace.rs:49
   8:  0x1070e6e - std::panicking::default_hook::{{closure}}::hfd1443ea3d275929
                       at src/libstd/panicking.rs:204
   9:  0x1070b33 - std::panicking::default_hook::h04f4c47c9d53b75b
                       at src/libstd/panicking.rs:224
  10:  0x107152c - std::panicking::rust_panic_with_hook::h82d86946573af827
                       at src/libstd/panicking.rs:472
  11:  0x10710d8 - rust_begin_unwind
                       at src/libstd/panicking.rs:380
  12:  0x10907b0 - core::panicking::panic_fmt::h8126505ca53cf226
                       at src/libcore/panicking.rs:85
  13:  0x10905b2 - core::option::expect_none_failed::h92f24811b2f30de5
                       at src/libcore/option.rs:1198
  14:   0x70473b - plume::main::hac8d852911614193
  15:   0x70e606 - std::rt::lang_start::{{closure}}::hfabbeff00a3d96ac
  16:  0x106ec56 - std::rt::lang_start_internal::{{closure}}::{{closure}}::h1b3708f4176810dc
                       at src/libstd/rt.rs:52
  17:  0x106ec56 - std::sys_common::backtrace::__rust_begin_short_backtrace::habb4ed333d8d62d9
                       at src/libstd/sys_common/backtrace.rs:129
  18:  0x1070f8f - std::rt::lang_start_internal::{{closure}}::hb2e445c8e07a7e30
                       at src/libstd/rt.rs:52
  19:  0x1070f8f - std::panicking::try::do_call::h8ec12ab02f09b41d
                       at src/libstd/panicking.rs:305
  20:  0x1077118 - __rust_maybe_catch_panic
                       at src/libpanic_unwind/lib.rs:86
  21:  0x1071a3c - std::panicking::try::h7bfc7bf8c289bbfa
                       at src/libstd/panicking.rs:281
  22:  0x1071a3c - std::panic::catch_unwind::hf1ff911fc948eea5
                       at src/libstd/panic.rs:394
  23:  0x1071a3c - std::rt::lang_start_internal::h43b6597864427830
                       at src/libstd/rt.rs:51
  24:   0x70d2a1 - main
  25: 0xb794ee91 - __libc_start_main
  26:   0x4bcf7b - <unknown>

How to fix

Until there is a "fix", this is how I was able to get by:

From docs:

# Get the latest version of the code
git pull origin master
git checkout PLUME_VERSION # Skip this step if you want to use master, and not a tagged release

# Build the front-end
cargo web deploy -p plume-front

# Update plm
cargo install --path plume-cli --force --features DATABASE
# Update plume
cargo install --path . --force --no-default-features --features DATABASE

# Run the migrations
plm migration run

# Restart your instance
# If you are using sysvinit
sudo service plume restart
# If you are using systemd
sudo systemctl restart plume

We need to add in:

# Get the latest version of the code
git pull origin master
git checkout PLUME_VERSION # Skip this step if you want to use master, and not a tagged release

# Build the front-end
cargo web deploy -p plume-front

# Update plm
cargo install --path plume-cli --force --features DATABASE
# Update plume
cargo install --path . --force --no-default-features --features DATABASE

# Run the migrations
diesal migration run
plm migration run

# Remove old search_index
rm -rf search_index

# Recreate search index
plm search init

# Restart your instance
# If you are using sysvinit
sudo service plume restart
# If you are using systemd
sudo systemctl restart plume

Consequently

Even though I checked out 0.5.0, the instance still shows version 0.4.0.

Bash error: ``` plume@hammurabi:~/Plume$ RUST_BACKTRACE=full /home/plume/.cargo/bin/plume Configuration read from /home/plume/Plume/.env thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: IndexCreationError', src/main.rs:126:18 stack backtrace: 0: 0x106e3d1 - backtrace::backtrace::libunwind::trace::h85c30131a0dec24e at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88 1: 0x106e3d1 - backtrace::backtrace::trace_unsynchronized::h921997e0546f34ae at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66 2: 0x106e3d1 - std::sys_common::backtrace::_print_fmt::h21982e53f592a106 at src/libstd/sys_common/backtrace.rs:77 3: 0x106e3d1 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h69c6e5980f3aaa11 at src/libstd/sys_common/backtrace.rs:59 4: 0x109243c - core::fmt::write::h0762c8ebcff34b38 at src/libcore/fmt/mod.rs:1057 5: 0x106790c - std::io::Write::write_fmt::h1371e7e0e42f565d at src/libstd/io/mod.rs:1426 6: 0x1070e6e - std::sys_common::backtrace::_print::h30f48ac6a25f64b4 at src/libstd/sys_common/backtrace.rs:62 7: 0x1070e6e - std::sys_common::backtrace::print::h102780d90ef5dd2b at src/libstd/sys_common/backtrace.rs:49 8: 0x1070e6e - std::panicking::default_hook::{{closure}}::hfd1443ea3d275929 at src/libstd/panicking.rs:204 9: 0x1070b33 - std::panicking::default_hook::h04f4c47c9d53b75b at src/libstd/panicking.rs:224 10: 0x107152c - std::panicking::rust_panic_with_hook::h82d86946573af827 at src/libstd/panicking.rs:472 11: 0x10710d8 - rust_begin_unwind at src/libstd/panicking.rs:380 12: 0x10907b0 - core::panicking::panic_fmt::h8126505ca53cf226 at src/libcore/panicking.rs:85 13: 0x10905b2 - core::option::expect_none_failed::h92f24811b2f30de5 at src/libcore/option.rs:1198 14: 0x70473b - plume::main::hac8d852911614193 15: 0x70e606 - std::rt::lang_start::{{closure}}::hfabbeff00a3d96ac 16: 0x106ec56 - std::rt::lang_start_internal::{{closure}}::{{closure}}::h1b3708f4176810dc at src/libstd/rt.rs:52 17: 0x106ec56 - std::sys_common::backtrace::__rust_begin_short_backtrace::habb4ed333d8d62d9 at src/libstd/sys_common/backtrace.rs:129 18: 0x1070f8f - std::rt::lang_start_internal::{{closure}}::hb2e445c8e07a7e30 at src/libstd/rt.rs:52 19: 0x1070f8f - std::panicking::try::do_call::h8ec12ab02f09b41d at src/libstd/panicking.rs:305 20: 0x1077118 - __rust_maybe_catch_panic at src/libpanic_unwind/lib.rs:86 21: 0x1071a3c - std::panicking::try::h7bfc7bf8c289bbfa at src/libstd/panicking.rs:281 22: 0x1071a3c - std::panic::catch_unwind::hf1ff911fc948eea5 at src/libstd/panic.rs:394 23: 0x1071a3c - std::rt::lang_start_internal::h43b6597864427830 at src/libstd/rt.rs:51 24: 0x70d2a1 - main 25: 0xb794ee91 - __libc_start_main 26: 0x4bcf7b - <unknown> ``` ## How to fix Until there is a "fix", this is how I was able to get by: **From docs:** ``` # Get the latest version of the code git pull origin master git checkout PLUME_VERSION # Skip this step if you want to use master, and not a tagged release # Build the front-end cargo web deploy -p plume-front # Update plm cargo install --path plume-cli --force --features DATABASE # Update plume cargo install --path . --force --no-default-features --features DATABASE # Run the migrations plm migration run # Restart your instance # If you are using sysvinit sudo service plume restart # If you are using systemd sudo systemctl restart plume ``` We need to add in: ``` # Get the latest version of the code git pull origin master git checkout PLUME_VERSION # Skip this step if you want to use master, and not a tagged release # Build the front-end cargo web deploy -p plume-front # Update plm cargo install --path plume-cli --force --features DATABASE # Update plume cargo install --path . --force --no-default-features --features DATABASE # Run the migrations diesal migration run plm migration run # Remove old search_index rm -rf search_index # Recreate search index plm search init # Restart your instance # If you are using sysvinit sudo service plume restart # If you are using systemd sudo systemctl restart plume ``` ## Consequently Even though I checked out 0.5.0, the instance still shows version 0.4.0.
igalic commented 2020-09-18 13:27:28 +00:00
Owner
Copy link

that last bit is a known issue #789

that last bit is a known issue https://git.joinplu.me/Plume/Plume/issues/789
👍 2
maxolasersquad commented 2020-09-18 14:36:58 +00:00
Copy link

I ran into this same problem. It actually started with the migration being unable to be ran.

plume@hamurabi:~/Plume$ plm migration run
Configuration read from /home/plume/Plume/.env
thread 'main' panicked at 'Failed to run migrations: NotFound', plume-cli/src/migration.rs:48:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
plume@hamurabi:~/Plume$ RUST_BACKTRACE=full plm migration run
Configuration read from /home/plume/Plume/.env
thread 'main' panicked at 'Failed to run migrations: NotFound', plume-cli/src/migration.rs:48:5
stack backtrace:
   0:   0x87eea1 - backtrace::backtrace::libunwind::trace::h85c30131a0dec24e
                       at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
   1:   0x87eea1 - backtrace::backtrace::trace_unsynchronized::h921997e0546f34ae
                       at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
   2:   0x87eea1 - std::sys_common::backtrace::_print_fmt::h21982e53f592a106
                       at src/libstd/sys_common/backtrace.rs:77
   3:   0x87eea1 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h69c6e5980f3aaa11
                       at src/libstd/sys_common/backtrace.rs:59
   4:   0x8a0a9c - core::fmt::write::h0762c8ebcff34b38
                       at src/libcore/fmt/mod.rs:1057
   5:   0x87ad4c - std::io::Write::write_fmt::h1371e7e0e42f565d
                       at src/libstd/io/mod.rs:1426
   6:   0x8818ee - std::sys_common::backtrace::_print::h30f48ac6a25f64b4
                       at src/libstd/sys_common/backtrace.rs:62
   7:   0x8818ee - std::sys_common::backtrace::print::h102780d90ef5dd2b
                       at src/libstd/sys_common/backtrace.rs:49
   8:   0x8818ee - std::panicking::default_hook::{{closure}}::hfd1443ea3d275929
                       at src/libstd/panicking.rs:204
   9:   0x8815b3 - std::panicking::default_hook::h04f4c47c9d53b75b
                       at src/libstd/panicking.rs:224
  10:   0x881fac - std::panicking::rust_panic_with_hook::h82d86946573af827
                       at src/libstd/panicking.rs:472
  11:   0x881b58 - rust_begin_unwind
                       at src/libstd/panicking.rs:380
  12:   0x89f220 - core::panicking::panic_fmt::h8126505ca53cf226
                       at src/libcore/panicking.rs:85
  13:   0x89f022 - core::option::expect_none_failed::h92f24811b2f30de5
                       at src/libcore/option.rs:1198
  14:   0x4a3a31 - plm::migration::run::hc34b1ef2c9ce5c89
  15:   0x4aebe5 - plm::main::he002989405e96731
  16:   0x49f376 - std::rt::lang_start::{{closure}}::hc5e16bc8cfd03194
  17:   0x87f726 - std::rt::lang_start_internal::{{closure}}::{{closure}}::h1b3708f4176810dc
                       at src/libstd/rt.rs:52
  18:   0x87f726 - std::sys_common::backtrace::__rust_begin_short_backtrace::habb4ed333d8d62d9
                       at src/libstd/sys_common/backtrace.rs:129
  19:   0x881a0f - std::rt::lang_start_internal::{{closure}}::hb2e445c8e07a7e30
                       at src/libstd/rt.rs:52
  20:   0x881a0f - std::panicking::try::do_call::h8ec12ab02f09b41d
                       at src/libstd/panicking.rs:305
  21:   0x886158 - __rust_maybe_catch_panic
                       at src/libpanic_unwind/lib.rs:86
  22:   0x8823ec - std::panicking::try::h7bfc7bf8c289bbfa
                       at src/libstd/panicking.rs:281
  23:   0x8823ec - std::panic::catch_unwind::hf1ff911fc948eea5
                       at src/libstd/panic.rs:394
  24:   0x8823ec - std::rt::lang_start_internal::h43b6597864427830
                       at src/libstd/rt.rs:51
  25:   0x4af441 - main
  26: 0xb79b9e91 - __libc_start_main
  27:   0x4995db - <unknown>

I resolved that by running the migration with diesel.

diesel migration run

After that plm migration run would run indicating that all migrations had been applied. That's when this reported issue became a problem.

plume@hammurabi:~/Plume$ RUST_BACKTRACE=full /home/plume/.cargo/bin/plume
Configuration read from /home/plume/Plume/.env
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: IndexCreationError', src/main.rs:126:18
stack backtrace:
   0:  0x106e3d1 - backtrace::backtrace::libunwind::trace::h85c30131a0dec24e
                       at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
   1:  0x106e3d1 - backtrace::backtrace::trace_unsynchronized::h921997e0546f34ae
                       at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
   2:  0x106e3d1 - std::sys_common::backtrace::_print_fmt::h21982e53f592a106
                       at src/libstd/sys_common/backtrace.rs:77
   3:  0x106e3d1 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h69c6e5980f3aaa11
                       at src/libstd/sys_common/backtrace.rs:59
   4:  0x109243c - core::fmt::write::h0762c8ebcff34b38
                       at src/libcore/fmt/mod.rs:1057
   5:  0x106790c - std::io::Write::write_fmt::h1371e7e0e42f565d
                       at src/libstd/io/mod.rs:1426
   6:  0x1070e6e - std::sys_common::backtrace::_print::h30f48ac6a25f64b4
                       at src/libstd/sys_common/backtrace.rs:62
   7:  0x1070e6e - std::sys_common::backtrace::print::h102780d90ef5dd2b
                       at src/libstd/sys_common/backtrace.rs:49
   8:  0x1070e6e - std::panicking::default_hook::{{closure}}::hfd1443ea3d275929
                       at src/libstd/panicking.rs:204
   9:  0x1070b33 - std::panicking::default_hook::h04f4c47c9d53b75b
                       at src/libstd/panicking.rs:224
  10:  0x107152c - std::panicking::rust_panic_with_hook::h82d86946573af827
                       at src/libstd/panicking.rs:472
  11:  0x10710d8 - rust_begin_unwind
                       at src/libstd/panicking.rs:380
  12:  0x10907b0 - core::panicking::panic_fmt::h8126505ca53cf226
                       at src/libcore/panicking.rs:85
  13:  0x10905b2 - core::option::expect_none_failed::h92f24811b2f30de5
                       at src/libcore/option.rs:1198
  14:   0x70473b - plume::main::hac8d852911614193
  15:   0x70e606 - std::rt::lang_start::{{closure}}::hfabbeff00a3d96ac
  16:  0x106ec56 - std::rt::lang_start_internal::{{closure}}::{{closure}}::h1b3708f4176810dc
                       at src/libstd/rt.rs:52
  17:  0x106ec56 - std::sys_common::backtrace::__rust_begin_short_backtrace::habb4ed333d8d62d9
                       at src/libstd/sys_common/backtrace.rs:129
  18:  0x1070f8f - std::rt::lang_start_internal::{{closure}}::hb2e445c8e07a7e30
                       at src/libstd/rt.rs:52
  19:  0x1070f8f - std::panicking::try::do_call::h8ec12ab02f09b41d
                       at src/libstd/panicking.rs:305
  20:  0x1077118 - __rust_maybe_catch_panic
                       at src/libpanic_unwind/lib.rs:86
  21:  0x1071a3c - std::panicking::try::h7bfc7bf8c289bbfa
                       at src/libstd/panicking.rs:281
  22:  0x1071a3c - std::panic::catch_unwind::hf1ff911fc948eea5
                       at src/libstd/panic.rs:394
  23:  0x1071a3c - std::rt::lang_start_internal::h43b6597864427830
                       at src/libstd/rt.rs:51
  24:   0x70d2a1 - main
  25: 0xb794ee91 - __libc_start_main
  26:   0x4bcf7b - <unknown>

Removing the search_index and then running plm search init fixed the problem.

I ran into this same problem. It actually started with the migration being unable to be ran. ```sh plume@hamurabi:~/Plume$ plm migration run Configuration read from /home/plume/Plume/.env thread 'main' panicked at 'Failed to run migrations: NotFound', plume-cli/src/migration.rs:48:5 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace. plume@hamurabi:~/Plume$ RUST_BACKTRACE=full plm migration run Configuration read from /home/plume/Plume/.env thread 'main' panicked at 'Failed to run migrations: NotFound', plume-cli/src/migration.rs:48:5 stack backtrace: 0: 0x87eea1 - backtrace::backtrace::libunwind::trace::h85c30131a0dec24e at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88 1: 0x87eea1 - backtrace::backtrace::trace_unsynchronized::h921997e0546f34ae at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66 2: 0x87eea1 - std::sys_common::backtrace::_print_fmt::h21982e53f592a106 at src/libstd/sys_common/backtrace.rs:77 3: 0x87eea1 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h69c6e5980f3aaa11 at src/libstd/sys_common/backtrace.rs:59 4: 0x8a0a9c - core::fmt::write::h0762c8ebcff34b38 at src/libcore/fmt/mod.rs:1057 5: 0x87ad4c - std::io::Write::write_fmt::h1371e7e0e42f565d at src/libstd/io/mod.rs:1426 6: 0x8818ee - std::sys_common::backtrace::_print::h30f48ac6a25f64b4 at src/libstd/sys_common/backtrace.rs:62 7: 0x8818ee - std::sys_common::backtrace::print::h102780d90ef5dd2b at src/libstd/sys_common/backtrace.rs:49 8: 0x8818ee - std::panicking::default_hook::{{closure}}::hfd1443ea3d275929 at src/libstd/panicking.rs:204 9: 0x8815b3 - std::panicking::default_hook::h04f4c47c9d53b75b at src/libstd/panicking.rs:224 10: 0x881fac - std::panicking::rust_panic_with_hook::h82d86946573af827 at src/libstd/panicking.rs:472 11: 0x881b58 - rust_begin_unwind at src/libstd/panicking.rs:380 12: 0x89f220 - core::panicking::panic_fmt::h8126505ca53cf226 at src/libcore/panicking.rs:85 13: 0x89f022 - core::option::expect_none_failed::h92f24811b2f30de5 at src/libcore/option.rs:1198 14: 0x4a3a31 - plm::migration::run::hc34b1ef2c9ce5c89 15: 0x4aebe5 - plm::main::he002989405e96731 16: 0x49f376 - std::rt::lang_start::{{closure}}::hc5e16bc8cfd03194 17: 0x87f726 - std::rt::lang_start_internal::{{closure}}::{{closure}}::h1b3708f4176810dc at src/libstd/rt.rs:52 18: 0x87f726 - std::sys_common::backtrace::__rust_begin_short_backtrace::habb4ed333d8d62d9 at src/libstd/sys_common/backtrace.rs:129 19: 0x881a0f - std::rt::lang_start_internal::{{closure}}::hb2e445c8e07a7e30 at src/libstd/rt.rs:52 20: 0x881a0f - std::panicking::try::do_call::h8ec12ab02f09b41d at src/libstd/panicking.rs:305 21: 0x886158 - __rust_maybe_catch_panic at src/libpanic_unwind/lib.rs:86 22: 0x8823ec - std::panicking::try::h7bfc7bf8c289bbfa at src/libstd/panicking.rs:281 23: 0x8823ec - std::panic::catch_unwind::hf1ff911fc948eea5 at src/libstd/panic.rs:394 24: 0x8823ec - std::rt::lang_start_internal::h43b6597864427830 at src/libstd/rt.rs:51 25: 0x4af441 - main 26: 0xb79b9e91 - __libc_start_main 27: 0x4995db - <unknown> ``` I resolved that by running the migration with `diesel`. ```sh diesel migration run ``` After that `plm migration run` would run indicating that all migrations had been applied. That's when this reported issue became a problem. ```sh plume@hammurabi:~/Plume$ RUST_BACKTRACE=full /home/plume/.cargo/bin/plume Configuration read from /home/plume/Plume/.env thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: IndexCreationError', src/main.rs:126:18 stack backtrace: 0: 0x106e3d1 - backtrace::backtrace::libunwind::trace::h85c30131a0dec24e at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88 1: 0x106e3d1 - backtrace::backtrace::trace_unsynchronized::h921997e0546f34ae at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66 2: 0x106e3d1 - std::sys_common::backtrace::_print_fmt::h21982e53f592a106 at src/libstd/sys_common/backtrace.rs:77 3: 0x106e3d1 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h69c6e5980f3aaa11 at src/libstd/sys_common/backtrace.rs:59 4: 0x109243c - core::fmt::write::h0762c8ebcff34b38 at src/libcore/fmt/mod.rs:1057 5: 0x106790c - std::io::Write::write_fmt::h1371e7e0e42f565d at src/libstd/io/mod.rs:1426 6: 0x1070e6e - std::sys_common::backtrace::_print::h30f48ac6a25f64b4 at src/libstd/sys_common/backtrace.rs:62 7: 0x1070e6e - std::sys_common::backtrace::print::h102780d90ef5dd2b at src/libstd/sys_common/backtrace.rs:49 8: 0x1070e6e - std::panicking::default_hook::{{closure}}::hfd1443ea3d275929 at src/libstd/panicking.rs:204 9: 0x1070b33 - std::panicking::default_hook::h04f4c47c9d53b75b at src/libstd/panicking.rs:224 10: 0x107152c - std::panicking::rust_panic_with_hook::h82d86946573af827 at src/libstd/panicking.rs:472 11: 0x10710d8 - rust_begin_unwind at src/libstd/panicking.rs:380 12: 0x10907b0 - core::panicking::panic_fmt::h8126505ca53cf226 at src/libcore/panicking.rs:85 13: 0x10905b2 - core::option::expect_none_failed::h92f24811b2f30de5 at src/libcore/option.rs:1198 14: 0x70473b - plume::main::hac8d852911614193 15: 0x70e606 - std::rt::lang_start::{{closure}}::hfabbeff00a3d96ac 16: 0x106ec56 - std::rt::lang_start_internal::{{closure}}::{{closure}}::h1b3708f4176810dc at src/libstd/rt.rs:52 17: 0x106ec56 - std::sys_common::backtrace::__rust_begin_short_backtrace::habb4ed333d8d62d9 at src/libstd/sys_common/backtrace.rs:129 18: 0x1070f8f - std::rt::lang_start_internal::{{closure}}::hb2e445c8e07a7e30 at src/libstd/rt.rs:52 19: 0x1070f8f - std::panicking::try::do_call::h8ec12ab02f09b41d at src/libstd/panicking.rs:305 20: 0x1077118 - __rust_maybe_catch_panic at src/libpanic_unwind/lib.rs:86 21: 0x1071a3c - std::panicking::try::h7bfc7bf8c289bbfa at src/libstd/panicking.rs:281 22: 0x1071a3c - std::panic::catch_unwind::hf1ff911fc948eea5 at src/libstd/panic.rs:394 23: 0x1071a3c - std::rt::lang_start_internal::h43b6597864427830 at src/libstd/rt.rs:51 24: 0x70d2a1 - main 25: 0xb794ee91 - __libc_start_main 26: 0x4bcf7b - <unknown> ``` Removing the `search_index` and then running `plm search init` fixed the problem.
iamdoubz commented 2020-11-23 03:05:30 +00:00
Author
Copy link

I just wanted to post so others could see. Closing.

I just wanted to post so others could see. Closing.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
1686a/resist-gone-sender
1686a/fast-fill
paginate-search-init
s3
fix-delete-user
timeline-cli
blog-title
signature
remove-dup-images
ldap-non-anon
drone-ci
DearRude/force-lang
igalic/go/async-all-mut
go/async
floreal/translations-update
missing-docs
RAOF/fix-arm64-build
epsilon-phase/authorized-fetch
upgrade
improve-the-editor-once-again
igalic/feat/custom-fairing-domains
feature/ldap
test/dotenv_error
fix-mobile-margin
0.7.2
0.7.1
0.7.0
0.6.0
0.5.0
0.4.0-alpha-4
0.3.0-alpha-2
0.2.0-alpha-1
Labels
Clear labels   
A: API

Related to the REST API

  
A: Backend

Code running on the server

  
A: Federation

Stuff related to Federation

  
A: Front-End

Related to the front-end

  
A: I18N

Translations, and related code

  
A: Meta

More about project management or code than the project itself

  
A: Security

   
Build

The building, or installation process of Plume

  
C: Bug

Something isn't working

  
C: Discussion

We need to talk

  
C: Enhancement

New feature or request

  
C: Feature

This is a new feature

  
Compatibility

Compatibility with different browsers, readers and OS

  
Dependency

Related to an external package that Plume uses

  
Design

UI/UX related issues and PRs

  
Documentation

   
Good first issue

Good for newcomers

  
Help welcome

Extra attention is needed

  
Mobile

Issues affecting only mobile UX

  
Rendering

How elements're rendered out for the end user

  
S: Blocked

Something else needs to be fixed first

  
S: Duplicate

This issue or pull request already exists

  
S: Incomplete

This PR is not complete yet

  
S: Instance specific

Issues concern a limited number of instances

  
S: Invalid

This doesn't seem right

  
S: Needs Voting/Discussion

Need to be discussed by the community (on Loomio)

  
S: Ready for review

This PR is ready to be reviewed

  
Suggestion

Proposed ideas worth considering

  
S: Voted on Loomio

This is issue has been created after a vote on Loomio

  
S: Wontfix

This will not be worked on

No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Plume/Plume#822
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?