Open wyattjsmith1 opened 2 years ago
Hey - this is indeed a little odd. Zellij is supposed to populate the PLUGIN_DIR
at runtime... could it be that it does not have write permissions for it or some such?
Hmm... here are the permissions. Owner should have write for all. I assume this wouldn't get executed by another user:
zsh ❯ ls -al '/Users/wys/Library/Application Support/org.Zellij-Contributors.Zellij/plugins'
total 0
drwxr-xr-x 3 wys staff 96 Sep 20 11:31 .
drwxr-xr-x 3 wys staff 96 Sep 20 10:51 ..
drwxr-xr-x 2 wys staff 64 Sep 20 11:31 data
If you try to run Zellij with --data-dir /tmp/temporary-zellij-data-dir
(possible creating said folder first), does it work?
/dotfiles on main +10 -57 [✘!] took 3s114ms
zsh ❯ mkdir /tmp/temporary-zellij-data-dir
/dotfiles on main +10 -57 [✘!] took 12ms
zsh ❯ zellij --data-dir /tmp/temporary-zellij-data-dir
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 zellij-server/src/wasm_vm.rs:236:28
╰─▶ Cannot resolve wasm bytes for plugin PluginConfig { path: "tab-bar", run: Pane(None), _allow_exec_host_cmd: false, location: Zellij(PluginTag("tab-bar")) }
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`.
Very odd... could you share how you installed Zellij?
I just noticed you mentioned you installed from brew in the original issue. I must admit I'm a little stumped by this - it seems like the executable you have does not have plugins for some reason (either that or it can't write to your hard-drive anywhere).
Would you be willing to try the musl executable from our release?
I tried to reproduce on my m1 mac by clearing DATA_DIR
and installing from brew, but it worked for me. If everything goes well you should end up with:
❯ tree Library/Application\ Support/org.Zellij-Contributors.Zellij/
org.Zellij-Contributors.Zellij
├── plugins
│ ├── compact-bar.wasm
│ ├── status-bar.wasm
│ ├── strider.wasm
│ └── tab-bar.wasm
└── VERSION
Are there by chance any errors in the logfile? The code that tries to write the plugins should log some errors from what I saw.
Here it is. It looks like it only has the standard error I pasted above. I also searched my entire filesystem for the plugins just to see if they are an incorrect location, and I couldn't find anything. Is there some way to force zellij to create these plugins again?
fd compact-bar.wasm /
For what it's worth, I tried uninstalling through brew
and installing with cargo
, and I have the same result.
Just to make sure I understand - you mentioned you got this error on both mac and windows? So you got the same error on two different computers using two different installation methods?
That is correct. I was actually tracing through the code, and found a way around the issue.
I noticed that on this line, we destruct an Attach
and only create the plugins if create
is set. It looks like create is only set in the cli. After reading some documentation, I found that I can run zellij session -c
, and it will run and create my session and the plugins.
I can then kill zellij, and start a new server with just zellij
, and this will work.
I want to emphasize I have no clue how the zellij codebase works, and just came to this conclusion by skimming the codebase with my limited rust knowledge. My guess is that somewhere, the default behavior for starting a new session does not call install_default_assets
.
I hope this helps, but as of now, I am unblocked.
That is correct. I was actually tracing through the code, and found a way around the issue.
I noticed that on this line, we destruct an
Attach
and only create the plugins ifcreate
is set. It looks like create is only set in the cli. After reading some documentation, I found that I can runzellij session -c
, and it will run and create my session and the plugins.I can then kill zellij, and start a new server with just
zellij
, and this will work.I want to emphasize I have no clue how the zellij codebase works, and just came to this conclusion by skimming the codebase with my limited rust knowledge. My guess is that somewhere, the default behavior for starting a new session does not call
install_default_assets
.I hope this helps, but as of now, I am unblocked.
I've just installed zellij through brew as well, I'm getting a "Received empty message from server" when i try running the strider plugin. Did a 'zellij setup --check' and its looking for plugins in Library/Application Support/org.Zellij-Contributors.Zellij/plugins And it looks like this doesn't exist at all. Any tips? I tried your session -c command but I believe there have been some changes in the CLI since and this does not work.
From a brand new Mac M1, I ran
brew install zellij
. When runningzellij
with my configuration ORzellij setup --clean
, I get the following:I read a similar ticket https://github.com/zellij-org/zellij/issues/1327, but this seemed unrelated as it involved a manual install, whereas this is installed through
brew
.On another note, I attempted this using brew on Windows through WLS (I know, this seems like a terrible idea), and I had the same result. At first, I thought it was because I was using a Mac package manager on a Linux system run on Windows, but this setup is a brand new Mac.
Info:
I'd like to note that
PLUGIN DIR
contains an emptydata
directory. Is there something I'm missing regarding installing the default plugins?