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

Error while loading compiled WASM plugin #452

Open
NoSequel opened this issue Aug 21, 2021 · 4 comments
Open

Error while loading compiled WASM plugin #452

NoSequel opened this issue Aug 21, 2021 · 4 comments

Comments

@NoSequel
Copy link

Description

Anytime I try to run a plugin I've compiled using the cargo-quill program I get the following error whenever running the feather server, thread 'main' panicked at 'Memory should be set on `WasiEnv` first'. My friend compiled it for me on their linux environment, and it did work for me.

Reproduction Steps

  1. Compile the plugin using cargo-quill build
  2. Drop the .plugin file into the server_directory/plugins/ folder
  3. Run the server

Screenshots and Logs

image

Your Environment

  • Operating System: Windows 10 & Vagrant CentOS VM
  • Feather Version: current main branch (0.1.0 or 0.6.0?)
@koskja
Copy link
Contributor

koskja commented Aug 21, 2021

Also happened to me, try compiling the plugin to native code as a temporary fix.

@NoSequel
Copy link
Author

Also happened to me, try compiling the plugin to native code as a temporary fix.

What do you mean compiling to native code? Just running cargo build --release? Because I saw a requirement for a metadata.json file inside of the .plugin file.

@koskja
Copy link
Contributor

koskja commented Aug 21, 2021

Try cargo-quill --release --native, this compiles the plugin to a native library that is wrapped in the .plugin file and doesn't suffer from wasm related issues.

@NoSequel
Copy link
Author

Alright, that seems to work. Thanks!

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

2 participants