Sorry, yeah, it is a php issue. The code generator is written in C++ and I primarily work in C++ so just ended up adding C++ in the subject line :).
Submitted a bug here (https://github.com/grpc/grpc/issues/13193) but this is already part of 1.6.0 release so I was wondering about any guidelines here. Normally, I'd want to upgrade grpc more frequently than protobuf. Thanks. On Monday, October 30, 2017 at 3:23:08 PM UTC-7, Kailash Sethuraman wrote: > > Hi Arpit, > > I think there might be a PHP issue here, we are looking into it, but not > sure how it's related to C++? (per the subject) > Also, any clarification on this in a bug on github would be super useful > too. > > Thanks! > > > On Monday, October 30, 2017 at 2:45:23 PM UTC-7, Arpit Baldeva wrote: >> >> Hi, >> >> Does grpc offer any guidelines around the compatibility between grpc and >> protobuf? Looks like recently when the 1.6 version bumped the protobuf >> support to 3.4.0, it started using a new php namespace option from it >> without putting in a version guard. This means that a prior version of >> protobuf can't be used with grpc 1.6 now. >> >> Thanks. >> > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/a88af25a-1839-47bd-986a-93b315a67988%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
