Anthony Dodd

Yea, I'm actually getting the same thing. I was previously using an agent sidecar, and that was working well enough, but now I am getting the same issue. I am...

Hey folks ... after far too much difficulty and random troubleshooting, I am happy to report that I've got this thing working as it should with the following constraints: ```toml...

Would be great to have this as a helm chart. Would resolve a lot of the issues with parameterization and such.

@andrenth I def agree with @stepancheg. A great pattern for error handling in grpc in general is to simply define a shared `Error` type which defines all of the core...

@andrenth sorry for the super late response. > However, doesn't embedding errors in responses like this make handling a stream response a bit weird? ... So, not necessarily. Whenever you...

Serving static content and handling gRPC requests are two very different things. It would be best to simply create a server which uses this lib for gRPC and then rocket,...

Hey all, thanks for getting back with me. All solid feedback, and after reviewing your comments a few times, I am left with a few questions & a few things...

@andrenth the idea is that if you choose to use nightly & enable proc macro, conservative impl trait & generators [as described here](https://github.com/alexcrichton/futures-await/blob/master/README.md#how-do-i-use-this), then you can simply decorate one of...

Yea, both types of futures. The question that needs to be answered is if the compiler will coerce our `Result` type (which is already being coerced into a `Future` when...

Hopefully I am answering your question effectively.