Thanks for the heads up, @apolcyn !

PTAL

There seems to be some differences between rubocop on these tests and my dev environment which I'm not sure is the exact cause yet, but is causing some delayed rubocop errors. Assuming those are now fixed, I think this should be ready for a look. rubocop errors should be resolved now, dev branches just need to be rebased to pick up new rubocop version

IMO the most tricky part of this was the added dependency on googleapis-common-protos-types and the loading of the google-protobuf message in the new utility file. But since we already have the google-protobuf dependency in the gemspec, and because there is no runtime loading of those protobuf messages unless the new utility used, this should not break any current usage.

FYI @qingling128

Any update on this PR, which is blocking the fix for googleapis/google-cloud-ruby#1438?

Thanks for checking @geigerj !
Hmm, seems there are some failed tests and it has not been reviewed yet.

squashing commits down before mering

mac tests saw pre-existing #12538, but sanity tests failed to build the docker image, so re-running sanity

interop tests passed but the test failed because of

ERROR: [GitHub Commit Status Setter] - {"message":"No commit found for SHA: eb464d3e6ba4b7dd04eb1058edddd7822e46618b","documentation_url":"https://developer.github.com/v3/repos/statuses/"}, setting build result to FAILURE

mac tests on failed with known kokoro/mac/ruby issue: #12538