Pierangelo Di Pilato
Pierangelo Di Pilato
> > can I take your branch and finish it or do you want to continue the implementation by yourself? > > If this is blocking you feel free to...
@houshengbo @matzew what do you think?
Yes, what I'm suggesting is that it doesn't have to be that way, services are completely different so it makes sense to have a separate field.
@houshengbo I didn't get your opinion on this fully, can you expand a little bit?
/remove-lifecycle stale /triage accepted
Currently, waiting on a condition with ``` kubectl wait deployment --timeout 300s --for=condition=Nope=True ``` waits even when the condition `Nope` doesn't exist, while waiting on a custom field with `jsonpath`...
Example use case where the wait with `jsonpath` fails immediately: ```bash $ kubectl create deployment nginx --image=nginx; kubectl wait --for=jsonpath='{.status.readyReplicas}'=1 deploy/nginx deployment.apps/nginx created error: readyReplicas is not found ``` instead...
I've seen this issue as well, at ~ 4 PM, I deployed a new version of our application without the circuit breaker and the memory consumption wasn't ever-growing anymore as...
An heap dump showed that there were many `byte[]` referenced by `VertxUnsafeHeapByteBuf`, that reference a `HttpResponseImpl` which is what our application returns as result of the `VertxCircuitBreaker.execute()` method (it's a...