Release google-cloud-python-happybase 0.32.0

[crwilcox]

This pull request was generated using releasetool.

[sduskis]

@crwilcox, it looks like there's a failing unit test. I'm going to try to rerun,

For posterity, here's the failure from TestBatch.test_send:

   self.assertEqual(table._low_level_table.rows_mutate,
                   [row1, row2])

This needs to be a comparison of sets rather than lists.

[crwilcox]

@sduskis Well, that is a thing. This PR should result in no code changes. That means we have had this failing in master :(

[tseaver]

Track merge of PR #53.

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

[tseaver]

@crwilcox I rebased the branch to pick up the unit test fix from #53.

[tseaver]

@crwilcox The lint failure is real: google.cloud.happybase.pool.Pool.__init__ actually does make an invalid call to google.cloud.happybase.connection._get_instance: its unit tests mock that away.

[tseaver]

Release should block on merge of #57, which fixes the real (not style) bug revealed by the lint failure.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

[crwilcox]

Release is at https://github.com/googleapis/google-cloud-python-happybase/releases/tag/google-cloud-python-happybase-2018.12.17