Comparing v2.18.2...v2.19.0 · googleapis/python-storage
This repository was archived by the owner on Mar 31, 2026. It is now read-only.
- 17 commits
- 30 files changed
- 8 contributors
Commits on Sep 27, 2024
Commits on Sep 28, 2024
-
build(python): release script update (#1345)
Source-Link: googleapis/synthtool@71a7297 Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-python:latest@sha256:e8dcfd7cbfd8beac3a3ff8d3f3185287ea0625d859168cc80faccfc9a7a00455 Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com> Co-authored-by: cojenco <cathyo@google.com>
3 people authored
Sep 28, 2024
Commits on Sep 30, 2024
Commits on Oct 9, 2024
-
fix: do not spam the log with checksum related INFO messages when dow…
…nloading using transfer_manager (#1357) * fix: do not spam the log with checksum related INFO messages when downloading using transfer_manager `download_chunks_concurrently` function does not allow to set `checksum` field in `download_kwargs`. It also does not set it on its own so it takes the default value of `"md5"` (see `Blob._prep_and_do_download`). Because ranged downloads do not return checksums it results in a lot of INFO messages (tens/hundreds): ``` INFO google.resumable_media._helpers - No MD5 checksum was returned from the service while downloading ... (which happens for composite objects), so client-side content integrity checking is not being performed. ``` To fix it set the `checksum` field to `None` which means no checksum checking for individual chunks. Note that `transfer_manager` has its own checksum checking logic (enabled by `crc32c_checksum` argument) * fix tests