Diego Marquez

CT4E has the option to include the `appengine-api` library, but not the client itself (`google-api-client-appengine`). It is not planned as a feature

Looks like the format check is failing ``` > Task :jib-core:verifyGoogleJavaFormat FAILED :jib-core:verifyGoogleJavaFormat (Thread[Execution worker for ':' Thread 2,5,main]) completed. Took 5.055 secs. FAILURE: Build failed with an exception. *...

Hi @CoderYellow, would you mind adding a bit more of context to this request (why do we need this, where exactly)? I see that the micronaut example is [_the_ place](https://github.com/search?q=repo%3AGoogleContainerTools%2Fjib%20developmentOnly&type=code)...

Hi @ChristianCiach, thanks for bringing this up. Since we are accepting contributions, the best way to determine if your suggestion is non-breaking is by running tests on a PR, so...

Hi @seqwait, thanks for reporting this. If possible, would you mind sharing a reproducer (snippet or project)? This could be a server side issue, so indicating the library with which...

The [docs of `RecordSet.Type`](https://cloud.google.com/java/docs/reference/google-cloud-dns/latest/com.google.cloud.dns.RecordSet.Type) do not show `DS` as a possibility. [googleapis/googleapis](https://github.com/googleapis/googleapis/tree/master/google/cloud) does not have the proto of DNS Apiary, however, [leaves it as a `String` field](https://github.com/googleapis/google-api-java-client-services/blob/fb0487d1c12f9859be916535f7fd02ca54fb2107/clients/google-api-services-dns/v1/2.0.0/com/google/api/services/dns/model/ResourceRecordSet.java#L75-L80)

Closing as not planned as App Engine applications running on JDK 1.8 have reached end of support

> I didn't read them correctly. the destination_name is library_name now. > > @diegomarquezp Would you update the document? Hi @suztomo, we have an [entry](https://github.com/googleapis/google-cloud-java/blob/main/generation/new_client_hermetic_build/README.md#library-name-library_name) in the action's readme. Which...

Hi @rnaval, thanks for reporting this. Would you mind sharing the tag of the docker image you are using? Has this occurred when running your java application on your host...

It looks like protobuf-java-util may be involved (thanks @suztomo).