Wasm panicked when launching strider

[Kahss]

zellij --version: 0.32.0 stty size: 48 211 uname -av: Linux LGOP3164 5.4.0-131-generic #147~18.04.1-Ubuntu SMP Sat Oct 15 13:10:18 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

List of interacting programs : zsh --version: zsh 5.4.2 (x86_64-ubuntu-linux-gnu)

Further information When running zellij --layout strider with RUST_BACKTRACE=1, the following error occurs (home name obfuscated for security reasons):

> zellij --layout strider

Error occurred in server:

  × Thread 'wasm' panicked.
  ├─▶ Originating Thread(s)
  │     1. ipc_server: NewClient
  │     2. pty_thread: NewTab
  │     3. screen_thread: NewTab
  │     4. plugin_thread: Load
  │   
  ├─▶ At /home/xxx/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmer-wasi-1.0.2/src/state/mod.rs:812:37
  ╰─▶ not implemented: Absolute symlinks are not yet supported

      Panic backtrace:
         0: <unknown>
         1: <unknown>
         2: <unknown>
         3: <unknown>
         4: <unknown>
         5: <unknown>
         6: <unknown>
         7: <unknown>
         8: <unknown>
         9: <unknown>
        10: <unknown>
        11: <unknown>
        12: <unknown>
        13: <unknown>
        14: <unknown>
        15: <unknown>
        16: <unknown>
        17: <unknown>

  help: If you are seeing this message, it means that something went wrong.
        Please report this error to the github issue.
        (https://github.com/zellij-org/zellij/issues)

        Also, if you want to see the backtrace, you can set the `RUST_BACKTRACE` environment variable to `1`.

[imsnif]

Strider doesn't yet support symlinks because of some downstream issues with wasmer. I agree it shouldn't panic, but this is the reason.

[Kahss]

Ok, thanks for the info.