Joshua Humphries

> so your proto2 change ends up being very loud @mkruskal-google, okay. I can remove that warning. I had mainly added it for symmetry/consistency with the analogous warnings that are...

> that seems to have fixed all the issues in our tests, so we can keep the warnings The rebase you pushed? Did it include any changes I should examine...

@mkruskal-google, do you have any idea what the _expected behavior_ of those files is? I guess the custom name was _only_ used for marshaling to JSON and not for unmarshaling?...

Also, do you mind pushing your local changes to this PR? Or do you want me to reproduce them and push them here? It sounds like maybe I should just...

@mkruskal-google, I just realized another validation check that should probably be done here, and it's one that should probably be an error even in proto2: the custom json name must...

> Provide an option to silence this error and restore the old behavior @mkruskal-google, do you mean a command-line option? If so, do you think that is something I can...

> Actually there's still the issue of the old error you replaced too. I don't quite follow. What error was replaced? I think I just added new errors (related to...

@Lucareful, @ghost: this is not a grpcurl issue as the problem is in the server, which does not correctly provide the reflection service due to the use of gogo. It's...

@jchadwick-buf, yes, I can confirm that this is fixed in 1.9.0. The issue has to do with how parallelism was achieved in earlier versions of buf: the list of all...

> Bummer. So what is the prescribed way of hosting in production? Dedicated subdomains? @lucasmaj, @d1820, do you mean for backend routing, like through a reverse proxy? If so, you...