Eyal Post

The example package I provided was just a way to demonstrate the issue. In reality our use case is more complicated (and we don't really have a place to do...

Wanted to try and convince you to either make it optional indeed for proto2 optionals or at least provide a flag which does this. Indeed proto2 expects deserializers to return...

Just encountered the same bug in our repo. We have a `prepare` script that only a few modules implement and the other (~30) modules don't need. Still I need this...

you have support for plugins? 🤔

+1 for client\server examples of handling details In Java it is also supported this via: ```java Status s = com.google.rpc.Status.newBuilder() .setCode(com.google.rpc.Code.INVALID_ARGUMENT.getNumber()) .setMessage("Invalid age") .addDetails(Any.pack(BadRequest.newBuilder() .addFieldViolations(BadRequest.FieldViolation .newBuilder() .setField("age") .setDescription("age must be...

Which other issue? The one I reported before was fixed. This is a different issue

Yes it does work. cc @sr01 which hopefully can verify whether it happens in the new version or not

I was going to open a feature request for the same thing and luckily found this 🙂 Yes, please! I think this should be the default. If anyone actually want...

Same here. Any new about this issue? ``` Logger: homeassistant.components.sensor Source: helpers/entity_platform.py:610 Integration: Sensor First occurred: 21:39:01 (6 occurrences) Last logged: 21:47:51 Platform rest does not generate unique IDs. ID...