…he plain text format (#3263)

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>

#3256)

* chore: Update generation configuration at Thu Aug 21 02:29:57 UTC 2025

* chore: Update generation configuration at Fri Aug 22 02:29:15 UTC 2025

* chore: Update generation configuration at Sat Aug 23 02:28:32 UTC 2025

* chore: Update generation configuration at Tue Aug 26 02:29:41 UTC 2025

* chore: Update generation configuration at Wed Aug 27 02:28:28 UTC 2025

* chore: generate libraries at Wed Aug 27 02:28:54 UTC 2025

#3267)

* chore: Update generation configuration at Thu Aug 28 02:27:30 UTC 2025

* chore: Update generation configuration at Fri Aug 29 02:27:47 UTC 2025

* chore: generate libraries at Fri Aug 29 02:28:19 UTC 2025

* chore: Update generation configuration at Sat Aug 30 02:25:00 UTC 2025

…67.0 (#3268)

…zy RPCs such as reads & writes pt.2 (#3277)

The initial attempt at this could leak scope and result in new spans being nested incorrectly. This approach attempts to be less clever, but bounds all scopes so there isn't any leaking.

Followup to #3255

… for large writes (#3278)

This main idea here is to allow async incremental clearing of the outbound queue even when large writes are performed.

Previously, when using the MinFlushStrategy, if a large write was performed (larger than maxPendingBytes) a single `flush: true state_lookup: true` would be sent to GCS, thereby making it so that no new writes could be accepted until the full `maxPendingBytes` where ack'd. This change updates so that if a write is larger than `minFlushSize` a message will be annotated `flush: true state_lookup: true`. This doesn't necessarily mean that a flush will be done every `minFlushSize` as the message packed can be up to 2MiB, this will simply annotate a message as `flush: true state_lookup: true` if it has been at least `minFlushSize` bytes since we sent a flush.

…v3.52.1 (#3280)

…shallow (#3273)

* chore: update BlobInfo.contexts diff handling to be deep rather than shallow

Add JsonUtils class to provide some helpers for performing arbitrarily deep
field selection. Our existing implementation is flat for everything exception
metadata, with the addition of object contexts we now have an N depth diff
(metadata is always depth 2, but a context path is
`contexts.custom.<key>.value`) and the value of the key is an object instead
of a string. We accomplish this arbitrary diffing by first flattening the src
object to a map of paths to leaves and their corresponding string values. Then
we diff the keys to produce a new map, and then treeify that new map back to a
json structure.

This is quite robust, but isn't terribly efficient so we only use it for
contexts and metadata fields.

Update BlobInfo.BuilderImpl#setContexts to deeply resolve the diff against the
provided value.

Update BlobInfo object contexts maps to use unmodifiable hashmaps instead of
ImmutableMap. ImmutableMap doesn't allow null values, but we need to accept
null values to allow customers to remove individual values.

Add object contexts to the existing ITNestedUpdateMaskTest.

gRPC didn't require any special handling as it's `update_mask` already takes
care of things appropriately after the deep diffing is added.

* chore: update method name

…#3271)

* chore: Update generation configuration at Tue Sep  2 18:22:51 UTC 2025

* chore: Update generation configuration at Wed Sep  3 02:25:52 UTC 2025

* chore: generate libraries at Wed Sep  3 02:26:23 UTC 2025

* chore: Update generation configuration at Thu Sep  4 02:24:44 UTC 2025

* chore: Update generation configuration at Fri Sep  5 02:26:57 UTC 2025

* chore: Update generation configuration at Sat Sep  6 02:24:19 UTC 2025

* chore: generate libraries at Sat Sep  6 02:24:56 UTC 2025

…r of bytes it should consume (#3279)

* chore: update ChunkSegmenter to optionally allow a limit on the number of bytes it should consume

Update BidiAppendableUnbufferedWritableByteChannel to only attempt to consume as many bytes as are available according to the stream -- this prevents over packing of segments we will for sure never be able to use.

* chore: fix blockSize reset logic

* chore(main): release 2.57.0

* chore: generate libraries at Tue Sep  9 17:26:06 UTC 2025

---------

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: cloud-java-bot <[email protected]>