Joshua Humphries
Joshua Humphries
@go-aegian, so the issue is that the knit-ts client won't accept the value in your example, produced by knit-go? If so, does it accept _any_ number of digits after the...
@go-aegian, I just saw your related issue in the connect-go repo. I also just double-checked the spec for the JSON format of a `google.protobuf.Timestamp` and it states that the portion...
I think you might be using an old version protobuf-es. The line you state is the problem looks like it was changed eight months ago to support fractional seconds in...
@jonavos, is your client doing any streaming, or is this only for unary RPCs?
@jonavos, thank you for reporting this and for indicating the likely culprit. I'll see if I can reproduce with that info.
@jonavos, I'm not having success reproducing. It is possible that your code is missing a `finally` block to close the stream returned from a streaming call? For a client-stream, you...
> Although it's worth noting that I don't see an exception propagating to my client code in these instances. Is it possible you are failing to exhaust the response stream...
> I've decided that this isn't correlated with the issues we've been seeing however so I'm happy for you to close this issue. No, let's leave it open. If your...
The issue seems to be that okhttp (or this repo's okhttp adapter) sometimes treats the closure of the HTTP 1.1 connection as a plain EOF (resulting in an unknown error...
@Smithx10, I see the documentation isn't particularly clear on this. But this is, in fact, expected. Each builder also includes a link _up_ to its parent. If you add a...