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

Plugin panics with <NO PAYLOAD> msg after update to 0.41.1 #21

Closed
ondrej-ivanko opened this issue Nov 6, 2024 · 2 comments
Closed

Plugin panics with <NO PAYLOAD> msg after update to 0.41.1 #21

ondrej-ivanko opened this issue Nov 6, 2024 · 2 comments

Comments

@ondrej-ivanko
Copy link

Hi,

since latests Zellij update the room plugin stopped working. I provided logs and my config.kdl

I provided relevant part of backtrace log with full details. I tried to reinstall zellij and I also have the latest version of room in .config/zellij/plugins dir.

The issue happens when I type a name of tab and then press enter to switch on it.

Thank you for you help.

ERROR  |zellij_server::plugins::z| 2024-11-06 08:38:36.447 [async-std/runti] [/home/oji/.cargo/registry/src/index.crates.io-6f17d22bba15001f/zellij-server-0.41.1/src/plugins/zellij_exports.rs:1762]: PANIC IN PLUGIN!

<NO PAYLOAD>

PanicInfo {
    payload: Any { .. },
    message: Some(
        called `Result::unwrap()` on an `Err` value: "invalid_key",
    ),
    location: Location {
        file: "src/main.rs",
        line: 101,
        col: 1,
    },
    can_unwind: true,
} 
ERROR  |zellij_server::plugins::w| 2024-11-06 08:38:36.461 [async-std/runti] [/home/oji/.cargo/registry/src/index.crates.io-6f17d22bba15001f/zellij-server-0.41.1/src/plugins/wasm_bridge.rs:712]: Failed to apply event to plugin 13

Caused by:
    0: error while executing at wasm backtrace:
           0: 0x66422 - panic_abort::__rust_start_panic::abort::h43a31cec08408e17
                           at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/panic_abort/src/lib.rs:83:17              - __rust_start_panic
                           at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/panic_abort/src/lib.rs:37:5
           1: 0x66035 - rust_panic
                           at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:755:25
           2: 0x66010 - std::panicking::rust_panic_with_hook::hd084a40442e42af7
                           at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:727:5
           3: 0x651e9 - std::panicking::begin_panic_handler::{{closure}}::h7b63d0dbcdd5afd8
                           at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:597:13
           4: 0x65116 - std::sys_common::backtrace::__rust_end_short_backtrace::h1c8caee1545e21bb
                           at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/sys_common/backtrace.rs:151:18
           5: 0x65926 - rust_begin_unwind
                           at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:593:5
           6: 0x6bfe8 - core::panicking::panic_fmt::hbc45cade774fd748
                           at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:67:14
           7: 0x72f2e - core::result::unwrap_failed::h75b87e1db5b0a6ed
                           at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/result.rs:1651:5
           8: 0x11940 - <unknown>!std::thread::local::LocalKey<T>::with::hd7f477d39024c07d
           9: 0x8db3 - <unknown>!update
    1: wasm trap: wasm `unreachable` instruction executed

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: start_thread
  12: __clone3 
INFO   |zellij_server::plugins::w| 2024-11-06 08:38:39.480 [wasm      ] [/home/oji/.cargo/registry/src/index.crates.io-6f17d22bba15001f/zellij-server-0.41.1/src/plugins/wasm_bridge.rs:318]: Bye from plugin 13

config.zip

Screenshot from 2024-11-06 09-12-32
Screenshot from 2024-11-06 09-12-44

@ghost
Copy link

ghost commented Nov 6, 2024

I also encountered the same issue.
There is a pending #20 which worked, waiting for it to be merged.

@ondrej-ivanko
Copy link
Author

fixed by #20

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

1 participant