When testing with a deadline in context, the timeout value is converted to nanosecond in grpc-timeout header.
But there is no check of the TimeoutValue range, which could result in the server rejecting the msg with protocol error.
The grpc spec specified that the TimeoutValue can contain at most 8 digits:
TimeoutValue → {positive integer as ASCII string of at most 8 digits}
tsloughter
commented
2 years ago
Hi,
When testing with a deadline in context, the timeout value is converted to nanosecond in grpc-timeout header. But there is no check of the TimeoutValue range, which could result in the server rejecting the msg with protocol error.
The grpc spec specified that the TimeoutValue can contain at most 8 digits:
Best regards, Tonny