Alexandre Lamarre

Was any progress made on this? If this is still something that would be nice to have, I'd be interested in taking a look

Awrsome! Should be fun to play around with

As a heads up I verified this also fixes the same issue we were seeing in #658

In `mockgen.go` GenerateMockInterface: ```go longTp, shortTp := g.formattedTypeParams(intf, outputPackagePath) ``` `longTp` is initialized as `[T notifier.Clonable[notifier.T]]` because : ```go for i, v := range it.TypeParams { if i != 0...

This happens at startup, and there is no `bucket-index.json.gz` file existing after before, during or after startup, it must be getting written to later with the null blocks

Content of the rules `bucket-index.json` file is : ``` version 1 blocks null block_deletion_marks [] updated_at 1660745155 ```

2022-08-17T16:10:42.026Z ERROR test.env.bench failed to send batch {"agent": "ba3cef75-82a2-42e3-9dcd-35ed7c27e464", "error": "server returned HTTP status 503 Service Unavailable: "} 12:10PM INFO actions.e2e.test._exec | #54 960.2 2022-08-17T16:10:42.032Z ERROR test.env.bench failed to send...

After fixing the cortex query syntax and unmarshalling for the SLO Status API, there is no HTTP response/latency data to measure for the prometheus server (because cortex uses remotewrite). Doesn't...

I added the uuid of the SLO objects as a prometheus label to all the generated recording, metadata & alerting rules, so we can better aggregate them individually & unify...

Looks like SLO status returning no data was a "bug" of the test environment & narrowed down my user story