• the ABI in the fork is not compatible any of Istio versions and the current Envoy's HEAD (therefore not compatible with the next tagged Envoy release)
• some of the bugs are fixed in the official versions and I don't think it makes sense to continue maintaining the fork

Context

• at the moment, our SDK doesn't provide support for writing "bootstrap extensions"
• in the meantime, such extensions represent a perfect use case for Timer API and Shared Queue API

Context

• proxy_on_vm_start

Blockers

• behaviour of this API is counter-intuitive - instead of being called exactly 1 time in Wasm VM lifecycle, it gets called multiple times

Context

• Rust doesn't support backtraces on wasm32 (neither is backtrace package)

Expected

• find a way for user to manually attach location to an error
  • use file!() and line!() macros to get the location where an error is created
  • probably, use an error handling package like anyhow that allows to associate a free-form context with an error

Context

• at the moment, proxy-wasm-rust-sdk uses wee_alloc unconditionally

Expected

• put use of wee_alloc behind a feature flag

Context

• native Envoy Network Filters can stop further processing of a TCP connection by using read_callbacks_->connection().close(...) API

Expect

• proxy-wasm spec should provide an equivalent ABI

Context

• host calls
  • proxy_dispatch_grpc_call
  • proxy_open_grpc_stream
  • proxy_send_grpc_call_message
  • proxy_cancel_grpc_call
  • proxy_close_grpc_call
• extension callbacks
  • proxy_on_grpc_call_response_header_metadata
  • proxy_on_grpc_call_response_message
  • proxy_on_grpc_call_response_trailer_metadata
  • proxy_on_grpc_call_close

Context

• proxy_resume_downstream
• proxy_resume_upstream

Blockers

• not implement by the version of Envoy we've been developing against

Context

• Envoy Timer API consist of
  • proxy_set_tick_period
  • proxy_on_tick

Blockers

• at the moment, proxy-wasm only supports setting 1 timer per "root context" (equivalent of Envoy Extension Factory singleton)
• it would be confusing to expose such API to HTTP Filter and Network Filter
• we could probably expose such API to AccessLogger, but it's not yet operational (envoyproxy/envoy-wasm#487)

Context

• proxy_on_queue_ready

Blockers

• this API doesn't make sense for HTTP Filter and Network Filter
• this API makes sense for AccessLogger, but it's not yet operational (envoyproxy/envoy-wasm#487)
• this API makes sense for "BootstrapExtension"

Context

• Follow up for #40

This is no longer maintained, so we shouldn't advertise people using this. https://github.com/proxy-wasm/proxy-wasm-rust-sdk is an alternative

• yank or at least deprecate from crates.io
• Add any deprecation notice to the Cargo.toml
• Add a notice to the README saying this is no longer maintained (to help people who don't notice the archive status)
• Archive this repository

Context

• Follow up for #39

Hi,

first thing first, great talk 😃 last week in envoyCon, it pushes me to try this week,

I was implementing a "pet" wasm filter in Rust with envoy-sdk and getenvoy, following the talk spirit, but I got the following error where I don't know what I am doing wrong? Is there anybody that can point me to a direction about Wasm missing malloc error message and how to troubleshoot this kind of error:

[2020-10-21 14:01:49.273][596220][debug][wasm] [bazel-out/k8-opt/bin/external/envoy/source/extensions/common/wasm/_virtual_includes/wasm_hdr/extensions/common/wasm/wasm_vm.h:45] WasmVm created envoy.wasm.runtime.v8 now active
[2020-10-21 14:01:49.273][596220][debug][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:106] Base Wasm created 1 now active
[2020-10-21 14:01:49.376][596220][error][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:123] Wasm VM failed Wasm missing malloc
[2020-10-21 14:01:49.376][596220][error][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:123] Wasm VM failed Failed to initialize Wasm code
[2020-10-21 14:01:49.376][596220][debug][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:164] ~Wasm 0 remaining active
[2020-10-21 14:01:49.376][596220][debug][wasm] [bazel-out/k8-opt/bin/external/envoy/source/extensions/common/wasm/_virtual_includes/wasm_hdr/extensions/common/wasm/wasm_vm.h:49] ~WasmVm envoy.wasm.runtime.v8 0 remaining active
[2020-10-21 14:01:49.377][596220][critical][main] [external/envoy/source/server/server.cc:101] error initializing configuration '/tmp/getenvoy_extension_run910790954/envoy.tmpl.yaml': Unable to create Wasm HTTP filter me.filters.http.envoy_digest_header_filter
[2020-10-21 14:01:49.377][596220][info][main] [external/envoy/source/server/server.cc:704] exiting

The code of the http filter can be found at https://github.com/jeremybaumont/envoy-digest-header-filter

Hi,
I followed the getting started https://www.getenvoy.io/tutorials/getting-started-http-filter-rust/

then I changed the filter, just to try the response, but after the first request the filter gets blocked

 if let Err(err) = &filter_ops.send_response(403,
                                                   &[("form", "envoy filter")],
                                                   Some(b"Access forbidden.\n")) {

            info!("error {}", &err);

        }
        info!("******* request sent");

        Ok(http::FilterHeadersStatus::StopIteration)

The first request works:

< HTTP/1.1 403 Forbidden                                                                                                                                                                                                             
< content-length: 18                                                                                                                                                                                                                 
< content-type: text/plain                                                                                                                                                                                                           
< form: envoy filter                                                                                                                                                                                                                 
< date: Sun, 10 Jan 2021 18:06:30 GMT                                                                                                                                                                                                
< server: envoy  

Then it doesn't work anymore.

Thank you for the sdk

Summary

• E.g., new flag https://github.com/envoyproxy/envoy/blob/f9c9c04faf99e2fa306891541ef2f30ce62aa596/include/envoy/stream_info/stream_info.h#L82-83

Context

• proxy_get_property
• proxy_set_property

Notice that proxy-wasm spec

• doesn't list supported properties
• doesn't say anything about the value/format of those properties

Expected

• introduce strongly-typed API for working with properties supported by Envoy

Context

• proxy_on_http_request_metadata
• proxy_on_http_response_metadata

Blockers

• not implement by the version of Envoy we've been developing against

Context

• proxy_call_foreign_function

Context

• apparently, Rust doesn't support stack unwinding on wasm32 arch
• which means that Wasm VM becomes unusable after the first panic

Notes

• it seems that emscripten os does support unwinding, so maybe wasm32-unknown-emscripten could help ?

Context

• Follow up for #41