Description

NoSequel

opened on Aug 21, 2021

Issue body actions

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

Your Environment

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

Activity

1. koskja commented on Aug 21, 2021

   

   koskja

   on Aug 21, 2021

   Contributor

   More actions

   Also happened to me, try compiling the plugin to native code as a temporary fix.
2. NoSequel commented on Aug 21, 2021

   

   NoSequel

   on Aug 21, 2021

   Author

   More actions

   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.
3. koskja commented on Aug 21, 2021

   

   koskja

   on Aug 21, 2021

   Contributor

   More actions

   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.
4. NoSequel commented on Aug 21, 2021

   

   NoSequel

   on Aug 21, 2021

   Author

   More actions

   Alright, that seems to work. Thanks!

Issue actions