Rationale:
Inaiohttp,.read() is the standard, high-level method for reading the full response body. It correctly handles internal state (like caching the body for subsequent calls), which is essential for compatibility with wrappers likeaiohttp-client-cache. Accessing.content.read() directly bypasses this logic, leading to empty responses when the stream has already been consumed or intercepted by the caching layer.

Benefits:

Robustness: Ensures correct behavior whengoogle-auth is used in conjunction withaiohttp wrappers or middleware.
Standards: Aligns withaiohttp best practices for consuming response bodies.

Risk Mitigation:

Behavior:_CombinedResponse is designed to load the full response into memory. Changing to.read() preserves this behavior exactly; it just uses a safer accessor.
Performance: Sinceaiohttp's.read() returns a reference to the bytes, there is no additional memory overhead compared to the previous implementation.
Internal: This change is internal to the transport adapter and does not alter the public API or behavior for users not using caching libraries.

PR created automatically by Jules for task3355868403646689815 started by@chalmerlowe

fix: use .read() instead of .content.read() in aiohttp transport

87e0959

Using .read() is more robust when working with caching libraries likeaiohttp-client-cache, which may cause .content.read() to return emptybytes on subsequent reads. .read() ensures the full body is returned.Fixes#1248

Copy link

Author

google-labs-julesbot commentedDec 19, 2025

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me toReactive Mode. When this mode is on, I will only act on comments where you specifically mention me with@jules. You can find this option in thePull Request section of yourglobal Jules UI settings. You can always switch back!

For security, I will only act on instructions from the user who triggered this task.

New to Jules? Learn more atjules.google/docs.

fix: use .read() instead of .content.read() in aiohttp transport

9485c59

Using .read() is more robust when working with caching libraries likeaiohttp-client-cache, which may cause .content.read() to return emptybytes on subsequent reads. .read() ensures the full body is returned.Fixes#1248