Lucas Kent

I have arrived at 2 possible designs to solve this problem. ## Derived names ```yaml --- sources: - redis: name: "redis" listen_addr: "127.0.0.1:6379" connection_limit: 3000000 chain: - Tee: behavior: Ignore...

This is now being tracked by https://github.com/shotover/shotover-proxy/pull/542

Closed by https://github.com/shotover/shotover-proxy/pull/698

There could be some value in instruction counting locally, but the main goal was to make CI bench results stable. benchmarking on a local machine should be stable enough that...

I'm closing this since transform compatiblity was largely resolved by https://github.com/shotover/shotover-proxy/issues/520 I think that any remaining incompatibilities should be resolved by making transforms follow the transform invariants.

The work in this PR could be a useful starting point for research into wasm/plugins for shotover. Personally I would like to see a radically different approach to the one...

I think the best way to do this would be to: 1. shotover flushes all pending requests/responses while halting the processing of new requests * This clears out any messages...

RedisSinkSingle, supports pubsub as of https://github.com/shotover/shotover-proxy/pull/645 Since this issue was largely exploring the problem space and we now have a pretty good idea of what the solution looks like, I'll...

Our current implementation for image building is robust enough. I'm not opposed to ever landing this change, but its not worth putting more time into at the moment.

I cant afford the time to work on this any time soon. Anyone else is free to take this on.