Erik Westra

This would be very usefull

I am experiencing this exact same issue in gitlab runners when running a few different jobs that are all using testcontainers. 4/5 of my jobs always pass and one job...

I'm not sure this is the answer that you are looking for, but I don't think this is a bug. When unit testing gin handlers you will likely want to...

I'll leave this for one of the maintainers do decide on as I'm not familiar enough with the project to know if this is behaving as intended or not.

> I guess it is because gin implements `ResponseWriter.WriteHeader()` differently from `net/http`'s implementation. After calling `.WriteHeader()` from `ctx.Status()`, gin defers sending the status code until `.WriteHeaderNow()` is called. `.WriteHeaderNow()` will...

What is it you are actually trying to do with the body and is there a specific reason you are doing it in the ModifyResponse function. I'm not sure if...

@suyashkumar Are you just referring to using any instead of interface{} wherever possible, if so I'd be happy to go through the repository (either in batches or all together, whatever...

> > In te UI we have slightly more complex sorting logic > > Ah... I think when commenting on #1930, I failed to realize that _both_ the API server...

Just for your clarity @krancour This test (from current main) shows how we sort in the frontend currently: ``` const testPromotions = [ running1, pending2, running3, pending4, succeeded5, failed6, unknown7,...

So are we moving this completely from frontend to backend then and keeping all the sorting logic in the backend?