Aleksei Surikov

> Another idea we discussed was to have an annotation, like shipper.booking.com/noop, that people would set to true to cause a rollout to happen. > The problem with these approaches...

Related: https://github.com/bookingcom/shipper/blob/35e77d70e4844f50883d4be2beeb11b9b7aa9057/cmd/shipper/main.go#L180.

If you're looking to optimise throughput in scenarios with many concurrent requests, there're [some](https://queue.acm.org/detail.cfm?id=2839461) [systems](https://blogs.dropbox.com/tech/2018/03/meet-bandaid-the-dropbox-service-proxy/) out there that adopted LIFO queues. Could be interesting to see if this strategy can...

Sure, I was just suggesting a different queueing discipline (LIFO vs FIFO).

I think there's a low hanging fruit here whereby we can just inspect the SSA form and check if one of the arguments to `net.Dial` is an `*ssa.Call` to `fmt.Sprintf`...

So it's assumed that code will run on the same machine it was built on? Using literally the same interpreter binary? If not, are you sure that building the same...

Right, I understand that. But my question still remains. Consider this. You build perl 5.24.0 on your build machine from source and then use it to build some Perl XS...

One thing to consider here is that many production systems wrap built–in panic calls to have errors reported to some error tracking system. Case in point: Uber's own zap (Panic,...