Jacob Wirth

I spent a little time looking at http toxics in the past, and have an example up here: https://github.com/xthexder/toxic-example/blob/master/http.go It only modifies responses, but a similar approach could be used...

Metrics would definitely be a useful addition, and is something I've thought about in the past, but never got around to implementing anything. The only issue I see with your...

I'm not sure how useful this is, since it's a fairly old PR, but some of the code in https://github.com/Shopify/toxiproxy/pull/132 might be helpful for this.

I've thought about this for things like protocol aware toxics where you could potentially mock out the backend server entirely. There's definitely a few applications for it, it's just a...

I think the timeout/non-blocking write changes have resolved the deadlocks in the bandwidth toxic. There's still some edge-case behavior to worry about if you plan on pausing a connection with...

I've built K4A successfully on an Arch Linux machine at home. I think it's unlikely that we'll officially support Arch Linux, but I can try and get you a list...

As it turns out, I was mistaken about building K4A on arch linux. Since Arch Linux provides extremely recent versions of Clang and GCC, some additional warnings are detected in...

I was able to build without any modification by installing the `libsoundio` AUR package.

A couple notes: We actually provide a udev rule in the git repo that is specific to Kinect: https://github.com/microsoft/Azure-Kinect-Sensor-SDK/blob/develop/scripts/99-k4a.rules Normally the depth engine is provided as part of the debian...

I'd like to point out, this toxic produces behavior that would never be seen in the real world, unless the server or client is actually sending corrupt data. TCP packets...