Carroll Vance
Carroll Vance
> That is a bit of an unusual way to do so, but sure as a new person to these processes, I do agree that this is maybe not so...
> A new package – like this PR – is definitely _not_ necessary ;) Point taken! I appreciate you taking the time to help me out despite my obvious inexperience...
It would be quite nice to have `tsit5` in the released version.
Looks like its the server, my guess is we are overloading it (500k messages/sec).
Closing this since its not an issue with the client.
Interesting. I'm not sure if this is an issue with gRPCClient or ProtoBuf. Maybe there is a scoping issue where if you use the module version of the autogenerated code...
@xgdgsc with the above example are you able to use `encode` on Line when the inner name is also `Line`? If not, that would be something specific to ProtoBuf.jl.
Closing as I think this is likely an issue with ProtoBuf.jl. All we do is call encode/decode via the public interface.
Yes, we should not be raising this exception here. Working on a fix now.
@xgdgsc is this happening with response or bidirectional RPC? Trying to narrow down exactly where the exception is not being handled properly. From first glance it appears all uses of...