Block benign warning from Google library (#2228)

[jessebrennan]

Author (check before every review)

• PR title references issue
• Title of main commit references issue
• PR is linked to Zenhub issue
• Added DCP/1 label _{or this PR does not target an hca/* branch}
• Created issue to track porting these changes _{or this PR does not need porting}
• Added r tag to commit title _{or this PR does not require reindexing}
• Added reindex label to PR _{or this PR does not require reindexing}
• Freebies are blocked on this PR _{or there are no freebies in this PR}
• Freebies are referenced in commit titles _{or there are no freebies in this PR}
• This PR is blocked by previous PR in chain _{or this PR is not chained to another PR}
• Added chain label to the blocking PR _{or this PR is not chained to another PR}
• Ran make requirements_update _{or this PR leaves requirements*.txt, common.mk and Makefile untouched}
• Added R tag to commit title _{or this PR leaves requirements*.txt untouched}
• Added reqs label to PR _{or this PR leaves requirements*.txt untouched}
• Documented upgrading of deployments in UPGRADING.rst _{or this PR does not require upgrading}
• Added u tag to commit title _{or this PR does not require upgrading}
• Added upgrade label to PR _{or this PR does not require upgrading}
• make integration_test passes in personal deployment _{or this PR does not touch functionality that could break the IT}
• Rebased branch on develop

Primary reviewer (before pushing merge commit)

• Checked reindex label and r commit title tag
• Rebased and squashed branch
• Sanity-checked history
• Build passes in sandbox _{or added no sandbox label}
• Reindexed sandbox _{or this PR does not require reindexing}
• Added PR reference to merge commit
• Moved linked issue to Merged
• Pushed merge commit to Github

Primary reviewer (after pushing merge commit)

• Moved freebies to Merged column _{or there are no freebies in this PR}
• Shortened chain _{or this PR is not the base of another PR}
• Verified that N reviews labelling is accurate
• Commented on demo expectations _{or labeled as no demo}
• Pushed merge commit to Gitlab _{or this changes can be pushed later, together with another PR}
• Reindexed dev _{or this PR does not require reindexing}
• Deleted PR branch from Github and Gitlab
• Unassign reviewer from PR

[codecov]

Codecov Report

Merging #2614 (d87560b) into develop (dd7ca3d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #2614   +/-   ##
========================================
  Coverage    83.38%   83.38%           
========================================
  Files          125      125           
  Lines        12919    12919           
========================================
  Hits         10772    10772           
  Misses        2147     2147           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dd7ca3d...d87560b. Read the comment docs.

[coveralls]

Coverage remained the same at 83.308% when pulling d87560b on issues/jessebrennan/2228-google-warning into dd7ca3d on develop.

[hannes-ucsc]

Does this really eliminate all the back traces from https://gitlab.dev.singlecell.gi.ucsc.edu/snippets/7#LC41?

[hannes-ucsc]

We may have discussed orally but I'd like to see a written response to

#2614 (review)

for the record. No bump.

[jessebrennan]

Yes, it suppresses this warning https://github.com/googleapis/google-api-python-client/blob/9a25cc84e5174e06a82ff74058a8648b79652872/googleapiclient/discovery_cache/__init__.py#L44 which is what logs the stack traces.

[hannes-ucsc]

For demo, disable the fix, show the warning, re-enable the fix and show that the warning disappears.