Thats a good observation. I believe the deformation comes from the variable runtime of the sin method. Even with the 100 micros sleep that I've put there, in reality it takes a different amount of time between each data point calculation, making the sine wave a bit wonky. This gets worse as more and more calculations are done in parallel

It's more likely to be the unaccuracy of Instant in rust. It's guaranteed to be non-decreasing, but not steady: https://doc.rust-lang.org/std/time/struct.Instant.html

> In other words, each tick of the underlying clock might not be the same length (e.g. some seconds may be longer than others). An instant may jump forwards or experience time dilation (slow down or speed up), but it will never go backwards

Ugh, too late to edit but I’m way off. It’s just scheduling variability, if a task gets more CPU time, it plots more of them near each other, and if it gets less, they’re farther apart.

(I had originally thought the code used the duration since the start as the input to the sin function, didn’t realize it’s just plotting a pre-allocated range.)

At least it's not "You wouldn't believe why we could not solve this bug!" :)

It's about issues that would have lasted for ten year, without the possibility to be fixed, if we hadn't discovered the root cause - the caching policy issue.

> It's about issues that would have lasted for ten year, without the possibility to be fixed, if we hadn't discovered the root cause

Don't all issues last forever without the possibility to be fixed if you don't discover the root cause?

I agree, poor title.

Probably an unfortunate case of copypasta

Interesting idea! You could configure it to be non writable.

Unfortunately there is a big downside - as a third party plugin you're not really allowed to destructively change the hosted environment.