5 ms·
> So what's happened here is there's a bug in in gRPC 1.8. Yeah I don't understand how this is vgo's problem. In the follup post it shows that they are impor
by RVuRnvbM2e 8y ago
> So what's happened here is there's a bug in in gRPC 1.8.
Yeah I don't understand how this is vgo's problem.
In the follup post it shows that they are importing the buggy gRPC version directly: https://codeengineered.com/blog/2018/golang-vgo-broken-dep-tree/ https://codeengineered.com/blog/2018/golang-vgo-broken-dep-t...
So doesn't that mean that they can just file a bug report upstream to get the regression fixed in 1.8.1, and exclude 1.8.0 in the meantime?
- dolmen 8y agoI agree. I don't see a vgo issue. The behavior in the example was broken by a release, but could have as well been restored by a patch release as restoring behaviour would not have broken the API. See https://news.ycombinator.com/item?id=17123583 https://news.ycombinator.com/item?id=17123583