Tom Coupland

Seeing the same when revendoring: verifying github.com/grpc-ecosystem/[email protected]: checksum mismatch downloaded: h1:Iju5GlWwrvL6UBg4zJJt3btmonfrMlCDdsejg4CZE7c= go.sum: h1:BWIsLfhgKhV5g/oF34aRjniBHLTZe5DNekSjbAjIS6c=

Adding the following to go.mod replace section gets things moving: github.com/grpc-ecosystem/go-grpc-middleware => github.com/grpc-ecosystem/go-grpc-middleware v1.0.0+incompatible

I have also just started to encounter a very similar problem with multi-part requests. Reducing the timeout causes the request to be timed out, but it doesn't look to see...

Encountered this NPE, or a very similar one, when negative testing my multi-part consumer implementation. To recreate throw an exception out of an implementation of start-partial.

This sounds like a great idea. Less is more, and what little there is should be tightly focused. :+1:

@gviedma i think that is what's being proposed. "The CLI would instead recursively call DELETE on each /trigger, /function and /app endpoint."

Is this not already happening in the fn_go layer due to this: https://github.com/fnproject/fn_go/commit/11f1fff5ffb3c29454a023bc385817435e50b8e2

Ah ok, I was only thinking to make it visible when DEBUG=1.

Metric overload is a worry for sure. It's easy to make em, but sometimes hard to track dwon where they come from. I would say that if this creates a...

Thanks for the pointer to our dist config, will hook that up. I thought about a white list, but that would get painful quick imo. The size limit should stop...