Tjerk Anne Meesters

I agree that mixing them is a bad idea; semantically I would say that `getFirst()` conveys "no side effects" better than `first()` which may reset internal pointers to get there.

Our use case is that we use cumulative distribution bins for latency metrics, so e.g. a request that takes 34 msec would have the following tags: `bin:gt_0, bin:gt_10, bin:gt_20, bin:gt_30`...

@shakuzen Sorry for the tardy reply on this. Would it be accurate to say that your suggestion is effectively to define the SLO within the app itself? I'm not sure...

This is primarily a workaround for your issue, but until a better fix is made available, this is what you could use instead ```ruby ticket.safe_update = true ticket.updated_stamp = DateTime.now.utc.iso8601(0)...

Does anyone have a script or capable IDE that can reformat the code easily and apply this in all the places?

@superjimpupcake The dependency on sockets has been added as part of 5817bfe4b04b6179f4d377f059e67a1b2d2e2e78 Not sure about the `-fPIC` compiler flags, AFAIK that should be set automatically as part of the `./configure`...

I think now with 5817bfe4b04b6179f4d377f059e67a1b2d2e2e78 in place we can probably talk about this again. IMO we can release the current procedural as a first version. I'll be glad to help...

While considering hacks, I would also like to point out that I have a suggested patch that would accomplish this idea very specifically for supplying multiple tags with the same...

:+1: for the rotation discontinuity fix; in my own fork I also keep the cumulative angle instead of sending deltas back to the caller to make it compatible with the...

bump