You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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}
Best regards,
Tonny
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: