Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Go vgo: Semantic Versioning and Human Error. Parent comment
But we are not seeing any change in that code (https://github.com/grpc/grpc-go/blob/master/server.go#L228) in the following releases. And I tried to look for an issue mentionning MaxMsgSize and found nothing. https://github.com/grpc/grpc-go/issues?utf8=%E2%9C%93&q=MaxM...
The fix that would restore the compatibility you claim seems obvious:
func MaxMsgSize(m int) ServerOption { return func(o *options) { o.maxSendMessageSize = m o.maxReceiveMessageSize = m } }
So if this is an issue, why is this not reported?
There are no comments on this comment yet.
But we are not seeing any change in that code (https://github.com/grpc/grpc-go/blob/master/server.go#L228) in the following releases. And I tried to look for an issue mentionning MaxMsgSize and found nothing. https://github.com/grpc/grpc-go/issues?utf8=%E2%9C%93&q=MaxM...
The fix that would restore the compatibility you claim seems obvious:
This fix could have been applied in a minor release to restore compatibility without breaking the API.So if this is an issue, why is this not reported?