Bob Aman

Just noticed that `wasm-tools component wit test_plugin.wasm` output shows `import wasi:http/[email protected]` but not `import wasi:http/[email protected]`, so presuming that's why... but I guess I'm not sure I understand why it's missing....

This include: https://github.com/bulwark-security/bulwark/blob/api-refactor/wit/platform.wit#L4

Getting a working build might require a new pull since I've made a few changes and fixes in the interim. Normal build step for the main `bulwark-cli` binary (I usually...

Sorry, looping back to this quite a bit later. Yeah, that might be it. That specific component isn't using `wasi:http/outgoing-handler`. I'll have to write one that does and re-check. Might...

Confirmed, once I recompiled a component that used `wasi:http/outgoing-handler` it started to show up.

Not currently no. I will likely revive it at some point, but I'm not currently using this in prod right now.

It expected `#` to be an instance of `Examples::BookCollectionAttribute`... and that failed? Am I reading that wrong? This code probably did cause that error, but I would argue that the...

Ah, interesting and good to know. The scenario we're hitting issues with is in Grape, which uses Virtus for coercion. If you declare a Rails model as the type of...

That's true, but `proxy` `transparent` does change it. And since there's poten

Bumped the close button. It's true that `realip` doesn't change the header but `proxy` `transparent` does and because `realip` changes the remote IP, in conjunction, they're really hard to debug....