Michael Warres
Michael Warres
The [proxy_get_header_map_value](https://github.com/envoyproxy/envoy/blob/788f26648d7ef73bd22b5ff6f343ac57fe923544/source/extensions/common/wasm/context.cc#L767-L768) hostcall currently only returns a single value, which doesn't accomodate headers that appear multiple times, such as [Set-Cookie](https://httpwg.org/specs/rfc6265.html#set-cookie). The next Proxy-Wasm ABI minor version should update `proxy_get_header_map_value` or...
Set INITIAL_HEAP=1MB and ALLOW_MEMORY_GROWTH=1 to reduce starting memory usage of plugins, but allow the heap to grow. Explicitly set STACK_SIZE (previously named TOTAL_STACK) to 1MiB. This is a middle ground...
Context: https://github.com/proxy-wasm/proxy-wasm-cpp-sdk/pull/158/files#r1702364332 It should be possible to build against the C++ SDK using `clang --target=wasm32-wasi` as opposed to Emscripten. SDK documentation should include steps to do that. Related: #169, #136,...
- Update v8.patch - Remove v8_include.patch which is no longer needed - Remove dependency on chromium_base_trace_event_common This PR is stacked on top of #411.
`std=c++20` is used by both [v8](https://github.com/v8/v8/blob/85019c919dc1d5166702e59928f798c82f553fbb/bazel/defs.bzl#L148) and [Envoy](https://github.com/envoyproxy/envoy/blob/dbb35fa0d4b61f29c6ae81aca2cbd88184207d18/.bazelrc#L68). Switching to use it overall will reduce build surprises when importing proxy-wasm-cpp-host into Envoy.
Parameterized tests that rely on getWasmEngines() to determine test cases are not actually being instantiated. I discovered this when I updated googletest to a more recent version that detects uninstantiated...
(This issue is semi-related to #64 "HTTP: add control of the end_of_stream flag", arguably they could be coalesced) In its section on [Buffers](https://github.com/proxy-wasm/spec/tree/main/abi-versions/v0.2.1#buffers), the v0.2.1 ABI spec says: > Access...
(This is somewhat related to #63, not sure if it's better to fold into that or keep as a separate issue) ext_proc filter supports the notion of a [processing mode...
Currently, if a plugin initiated an outbound gRPC or HTTP call, the response to that call is dispatched in a callback for which the effective context is the root context...
Envoy currently patches proxy-wasm-cpp-host in order to build: [bazel/proxy_wasm_cpp_host.patch](https://github.com/envoyproxy/envoy/blob/acddf23bd01736ce2c230fbd66a02365aa7a21ae/bazel/proxy_wasm_cpp_host.patch). We should update proxy-wasm-cpp-host to make this patch unnecessary, if possible. @cpakulski FYI