-
Notifications
You must be signed in to change notification settings - Fork 14
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
How do you use this repository to test? #11
Comments
This framework currently implements only Proxy-Wasm ABI v0.1.0, wheras all existing SDKs implement Proxy-Wasm ABI v0.2.x. You might try using it with Proxy-Wasm Rust SDK v0.1.4 (latest release, still using Proxy-Wasm ABI v0.1.0) instead of the master branch, but I'm not sure if that still works, since the test framework is currently unmaintained (although, I hope to revive it later this year). |
Thanks for the info. I saw this issue #2 but ignored it when I saw the if else statements. Have you guys looked at what kubebuilder does in terms of setting up a ready to go project. https://github.com/kubernetes-sigs/kubebuilder. I have spun up a few operators using this and the scaffolding and annotation driven approach makes it fast to write, test and get into production. I would like to help. I suck at writing code that I cannot test in a lazy way. I haven't quite understood why rust's
|
@janitha09 Have you resolved this issue yet? I don't see the test framework being pulished, do we have to pull this repo locally and build with our implementation together? |
I tried this
~/gh/proxy-wasm/proxy-wasm-rust-sdk$ bazel build //examples:hello_world
the output looks like this
Then in the test-framework project I did this
following that I tried this
cargo run --example hello_world ~/gh/proxy-wasm/proxy-wasm-rust-sdk/bazel-bin/examples/hello_world.wasm
The output looks like this
Why is this saying the abi version is unsupported?
The backtrace implies that I am calling improperly i.e. the wasm is not loaded
What is the correct way to call it?
The text was updated successfully, but these errors were encountered: