dj95 / zjstatus

A configurable statusbar plugin for zellij
MIT License
435 stars 9 forks source link

Cannot load the plugin #6

Closed mostafaqanbaryan closed 12 months ago

mostafaqanbaryan commented 1 year ago

Hi. First of all, thank you for the great job you've done! Unfortunately, I cannot use the plugin. In zellij log I get:

INFO   |zellij_server::plugins   | 2023-09-11 13:33:01.855 [wasm      ] [zellij-server/src/plugins/mod.rs:137]: Wasm main thread starts
WARN   |zellij_utils::ipc        | 2023-09-11 13:33:02.972 [router    ] [zellij-utils/src/ipc.rs:222]: Error in IpcReceiver.recv(): InvalidMarkerRead(Error { kind: UnexpectedEof, message: "failed to fill whole buffer" })
ERROR  |zellij_client            | 2023-09-11 13:33:02.972 [router    ] [zellij-client/src/lib.rs:348]: Received empty message from server

And nothing. I used the default config in the document and even added first_start: "true", but didn't change anything.

dj95 commented 1 year ago

Hi, first of all thanks!

Can you please provide some more details? Here's a quick list, that makes debugging a bit easier.

With these information I can try to reproduce your error. first start is not needed anymore.

mostafaqanbaryan commented 1 year ago

Of course!

If you need anymore information, I'd be happy to help.

dj95 commented 1 year ago

Can you test with the absolute path without $HOME? I'm not sure if zellij is able to resolve the reference.

mostafaqanbaryan commented 1 year ago

Can you test with the absolute path without $HOME? I'm not sure if zellij is able to resolve the reference.

Nope, didn't work. If I load a plugin with wrong path, zellij says ERROR IN PLUGIN. But if it's right, it'll close and echos Received empty message from server

dj95 commented 1 year ago

Hmm, which OS do you use and how did you install zellij? I'll test it later then.

mostafaqanbaryan commented 1 year ago

Thank you

dj95 commented 1 year ago

Unfortunately I cannot reproduce the issue :/ I've set up a fresh PopOS vm and downloaded the releases as you did. As you can see in the screenshot, it's working.

I've created sha256 sums of the files, so you are able to verify, if we use the same.

20230911_20h01m54s_grim

mostafaqanbaryan commented 1 year ago

Unfortunately I cannot reproduce the issue :/ I've set up a fresh PopOS vm and downloaded the releases as you did. As you can see in the screenshot, it's working.

I've created sha256 sums of the files, so you are able to verify, if we use the same.

20230911_20h01m54s_grim

Thank you for taking the time and testing. Let me test again and check the sums, maybe I did something wrong.

mostafaqanbaryan commented 1 year ago

Oddly enough, everything's the same: image Maybe it has something to do with my setup. Anyway, thank you for the time!

dj95 commented 1 year ago

I were just able to recreate a similar issue with an older zellij version. Can you try to run zellij with the absolute path and then passing the arguments? Just in case there'a somewhere an older binary in $PATH.

Otherwise I don't really have an idea, what goes wrong :/ sorry

mostafaqanbaryan commented 1 year ago

Unfortunately didn't work. Looks like this happened in here too.

dj95 commented 12 months ago

Hi @mostafaqanbaryan ,

I don't know if you still bother with the problem, but I managed to reproduce it (by accident  😅) on macOS.

It happened, when I tried the current development version of zellij, which updated the WASM sandbox.

To fix the issue, I had to close all zellij instances and clean the cache under ~/Library/Caches/org.Zellij-Contributors.Zellij. Under linux it should be at ~/.cache/zellij.

Maybe it fixes the issue for you as well.

mostafaqanbaryan commented 12 months ago

Hi @mostafaqanbaryan ,

I don't know if you still bother with the problem, but I managed to reproduce it (by accident  😅) on macOS.

It happened, when I tried the current development version of zellij, which updated the WASM sandbox.

To fix the issue, I had to close all zellij instances and clean the cache under ~/Library/Caches/org.Zellij-Contributors.Zellij. Under linux it should be at ~/.cache/zellij.

Maybe it fixes the issue for you as well.

I didn't even know there was a cache! Removing the cache fixed it, Thank you!