martijneken

+1 crate_universe is the way

Sorry, I missed this comment until now! > target 'fuchsia' not declared in package 'os' Why are rust builds targeting fuchsia here? Have you tried using `supported_platform_triples` to limit the...

Different idea: since the issue is a missing platform, you should be able to upgrade Bazel platform rules in WORKSPACE: https://github.com/bazelbuild/platforms/releases/tag/0.0.9 ``` load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") http_archive( name = "platforms", urls =...

Test failures, looking...

Looks like a failure to serialize proxy_wasm::WasmResult in testing::internal::UniversalPrint (with GCC). Can't repro locally.

Hi folks, I don't have a direct answer, but in case it helps I'm working on an emsdk update in https://github.com/proxy-wasm/proxy-wasm-cpp-sdk/pull/157, bumping emsdk from v3.1.7 to v3.1.44. I ran into...

I am trying to understand https://github.com/proxy-wasm/proxy-wasm-cpp-host/pull/95 better. In that PR people asked why FilterHeadersStatus::StopIteration exists. I understand why it's a bad idea paired with sendLocalReply(), which should terminate the filter...

>> There is no way for ProxyWasm to 'consume and replace' the header/body data. > The whole ABI is about modifying streamed headers, body data, and trailers. Right, I worded...

What host proxy are you integrating with? Is this a chunking / buffering issue? (are you getting multiple 615 byte body chunks?)

+1 we should do this. I tried as part of my emsdk update (to fix a zlib issue) and I ran into some issues propagating copts: https://github.com/proxy-wasm/proxy-wasm-cpp-sdk/pull/157#discussion_r1297643204 I propose we...