GeezerVison

The docstring for log_transport_attempt states that successful transport attempts are defined as "2xx HTTP or OK gRPC", and that it emits logs for "retry/redirect/failure" attempts. However, using < 400 treats HTTP 3xx redirect status codes as successful attempts, causing them to return early and not be logged. To align the implementation with the docstring and ensure redirects are logged, the threshold should be < 300.

The < 400 threshold in _is_failed_attempt is intentional: per OpenTelemetry HTTP semantic conventions (and Google Cloud APIs that use 308 Resume Incomplete), only HTTP status codes >= 400 represent failed HTTP wire attempts. Updated the log_transport_attempt docstring to clarify < 400 HTTP or OK gRPC.

Catching BaseException will capture system-level interrupts such as KeyboardInterrupt and SystemExit, logging them as failed transport attempts. It is safer and more precise to catch Exception instead, ensuring that only actual runtime errors are logged while system interrupts propagate cleanly without side-effects.

Added an explicit except (KeyboardInterrupt, SystemExit, GeneratorExit): raise pre-guard before except BaseException as exc: (matching _GapicCallable._trace_span) so process-level interrupts propagate without emitting transport attempt logs while still capturing asyncio.CancelledError.