zellij: Layout strider crashes on macOS M1

Hi guys,

I don’t know how the wasmer-wasi code is being called here, but attempting to use zellij --layout strider on macOS (M1) panics with the following (reaches an unimplemented! macro):

$ zellij --layout strider
Originating Thread(s):
1. ipc_server: NewClient
2. ipc_server: NewClient
3. pty_thread: NewTab
4. screen_thread: ApplyLayout
5. plugin_thread: Load

Error: thread 'wasm' panicked at 'not implemented: Absolute symlinks are not yet supported': /Users/<user>/.cargo/registry/src/github.com-1ecc6299db9ec823/wasmer-wasi-1.0.2/src/state/mod.rs:812
   0: backtrace::backtrace::trace
   1: backtrace::capture::Backtrace::new
   2: zellij::common::errors::handle_panic
   3: std::panicking::rust_panic_with_hook
   4: std::panicking::begin_panic_handler::{{closure}}
   5: std::sys_common::backtrace::__rust_end_short_backtrace
   6: _rust_begin_unwind
   7: core::panicking::panic_fmt
   8: wasmer_wasi::state::WasiFs::get_inode_at_path_inner
   9: wasmer_wasi::syscalls::path_filestat_get
  10: <Func as wasmer::externals::function::inner::HostFunction<(A1,A2,A3,A4,A5),Rets,wasmer::externals::function::inner::WithEnv,Env>>::function_body_ptr::func_wrapper

Calling just zellij works normally.

Basic information

zellij --version: tested with 0.8.0 (Homebrew) and 0.11.0 (Cargo) tput lines: 25 tput cols: 80 uname -av or ver(Windows): Darwin hostname.local 20.4.0 Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:41 PDT 2021; root:xnu-7195.101.2~1/RELEASE_ARM64_T8101 arm64

List of programs you interact with as, PROGRAM --version: iTerm 3.4.6

Further information Reproduction steps, noticable behavior, related issues etc

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Reactions: 8
  • Comments: 18 (11 by maintainers)

Most upvoted comments

@jacksonfernando i just downgraded to 0.38.2 on macOS. Haven’t had the chance to investigate further. 🫤

Of course! That would be great

@ken-matsui No problem, also thanks for finding the issue!

cc @varac, we found the issue.

@a-kenji I could reproduce this; also, I hid the first comment to avoid confusing anyone. Thank you!

I found an issue related to this PR. For someone being concerned about progress, I link it:

Thank you so much! I’ll try it!