Rahul

With just the wasm filter in the config file, i see the expected body/header in the response from the proxy. However, the issue is I get a 503 Service Unavailable...

Thanks for the details. My goal is to utilize nighthawk client-server framework and implementation to measure perf impact of one or more filters, wasm filter for example. Does the following...

Ah, thanks! So apart from optional features like `cranelift`, other features which are enabled in wasmtime crate (pooling-allocator for example below) will be applied as well right? `pooling-allocator = ["wasmtime-runtime/pooling-allocator"]`...

I am facing same error - cannot register with non-github account.

@PiotrSikora Any issue with enabling this? After enabling default features, a second PR will enable us to support VTune for wasmtime ( a small change in `wasmtime.cc` in this repo)...

2. > What's the justification for enabling default features? I can just enable one feature, 'vtune' instead of all default features. I just assumed Cargo.toml here is following `wasmtime/crates/c-api/Cargo.toml` in...

>vtune is not c-api feature Right, I was planning on enabling it for the `wasmtime` dependency in c-api, similar to how cranelift is enabled (i would add back `default features...

PR (1/2) opened for updating wasmtime, https://github.com/proxy-wasm/proxy-wasm-cpp-host/pull/368

FWIW - While working on windows CI failures for my other PR, I noticed similar issue when I tried with msvc 2022. It seems to be due to msvc 2022...

I just updated wasmtime in `repositories.bzl` , and it ran the failing test successfully. I suspect the failures here were due to that. Let me take a look at `rules_rust`...