Rob Jansen

We need to discuss with @sporksmith, who is away for a bit. But we'll get back to you soon!

This is tricky, but I think I'm leaning toward some flavor of the opt-in options telling shadow to ignore missing features. When Shadow was mainly used for running Tor simulations,...

Is it worth also running a manual Tor benchmark? Because of the better tooling, I think that'll give us the overall system memory usage too (i.e., because we're running `free`...

From the benchmarks:  

@stevenengler is this fixed by the changes in #2632?

Oh boy, that seems bad! Could be the last rng leak causing some non-determinism I've anecdotally noticed.

See also https://github.com/shadow/shadow/discussions/2737

Note that the 100% reliability of control packets only applies to network graphs links that set a positive packet loss rate. In other words, no matter what you set as...

A workaround in the short term is to avoid calling `io.Copy` from go code. Instead, you could call the following function, which mirrors go's internal implementation but does not make...

@stevenengler I wonder if, instead of the try/commit scheme you outlined, we instead support a new interface called something like `splice_from` or `read_from` that we would call on the splice...