You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Compile the plugin using cargo-quill build
Drop the .plugin file into the server_directory/plugins/ folder
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?)
The text was updated successfully, but these errors were encountered:
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.
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.
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
cargo-quill build
.plugin
file into theserver_directory/plugins/
folderScreenshots and Logs
Your Environment
The text was updated successfully, but these errors were encountered: