Dylan Hitt
Dylan Hitt
Yeah. I was just saying you should base you should rebase on #319 which is now just in main. #319 isn't going this fix the issue. You seemed to bo...
I believe #508 allows for this to be closed
+1. This i still very much an issue for us as well. HPA/Karpenter cannot scale quick enough to absorb a spike in load. Our registry operates in a very burst...
Imma assign this to myself if that’s cool.
@Redict you may want to give the latest frida-core a try? I was experiencing a similar issue and has gone away since bumping to latest.
Oh interesting. I was able to pinpoint what appears to be causing this. Basically when ever the option of `option.DefaultStatusCode(201),` status code is set. I set it to 200 as...
Yeah it's because where we're calling `SetDefaultStatusCode` under the hood we're calling `WriteHeader` and that's the response being read by curl.
Looking through this the only thing we can really do here is attempt to infer the return type for the response before we call `SetDefaultStatusCode`. This seems to align with...
Okay a bit of a proposal `ContextFlowable` interface should be changed too: ```golang type ContextFlowable[B any] interface { ContextWithBody[B] // Serialize serializes the given data to the response. Serialize(data any,...
Are you using the option of DefaultStatusCode?