Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

live.connect() (Vertex AI) resolves ADC and refreshes the OAuth token synchronously on the event loop on every connect

オープン
  • 何か問題がありますか？
#3,056 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
74/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
google-cloud, python
領域
authentication, backend-api-design, performance

調査の方向性

Start in google/genai/live.py at AsyncLive.connect() and compare its Vertex AI authentication path with _api_client._async_access_token() and async_get_token_from_credentials(). Check the existing Live and auth tests before making a change. Done means ADC is cached per client, refresh work happens off the event loop, and the reported connect-time stalls and repeated refreshes are covered by tests.

索引モデルが issue の本文から書いたものです。

説明

Environment
  • google-genai 2.24.0, google-auth 2.58.0, Python 3.12
  • Vertex AI backend (GOOGLE_GENAI_USE_VERTEXAI=true), service-account ADC
  • Live API with many concurrent sessions per process (telephony voice agent)
What happens

On Vertex, AsyncLive.connect() (google/genai/live.py, ~L1055-1069) runs this before it opens the websocket:

if not self._api_client._credentials:
    creds, _ = google.auth.default(scopes=[...])   # sync, on the event loop
else:
    creds = self._api_client._credentials
if not (creds.token and creds.valid):
    auth_req = _auth_requests().Request()
    creds.refresh(auth_req)                         # sync HTTP, on the event loop

Two problems:

  1. Blocking I/O inside an async API. creds.refresh() makes a synchronous requests call to the token endpoint, on the event loop. Every other coroutine in the process stalls until it returns. For us that is live audio for every other call on the pod.
  2. No caching when the client was built without credentials=. The resolved credentials are a local variable and are never stored on _api_client. Every connect() therefore runs google.auth.default() again and refreshes a fresh, token-less credentials object. The sync refresh runs on every connect, not once an hour.

The async REST path already handles both. _api_client._async_access_token() loads auth via asyncio.to_thread(load_auth, ...) under an async lock and caches it in self._credentials. async_get_token_from_credentials() refreshes via asyncio.to_thread(refresh_auth, ...), only when expired.

Repro
import asyncio, time
from google import genai

async def ticker(stop, worst):
    while not stop.is_set():
        t = time.perf_counter(); await asyncio.sleep(0.01)
        worst[0] = max(worst[0], (time.perf_counter() - t - 0.01) * 1000)

async def main():
    client = genai.Client()  # Vertex via env, no credentials= passed
    for i in range(3):
        stop, worst = asyncio.Event(), [0.0]
        tk = asyncio.create_task(ticker(stop, worst))
        await asyncio.sleep(0.05)  # let the ticker start before connect() blocks
        async with client.aio.live.connect(
            model="gemini-live-2.5-flash-native-audio",
            config={"response_modalities": ["AUDIO"]},
        ):
            pass
        stop.set(); await tk
        print(f"connect #{i+1}: max event-loop stall {worst[0]:.0f} ms")
    await client.aio.aclose()

asyncio.run(main())

Output (Vertex, us-central1). I also counted service_account.Credentials.refresh calls:

connect #1: max event-loop stall 517 ms, token refreshes during connect: 1
connect #2: max event-loop stall 410 ms, token refreshes during connect: 1
connect #3: max event-loop stall 415 ms, token refreshes during connect: 1

Expected: auth resolved once per client, refresh only near expiry, and never on the event loop. Stalls should be a few ms.

Suggested fix

In AsyncLive.connect(), reuse the async REST path: await self._api_client._async_access_token(). That loads ADC off-loop, caches it on the client, and refreshes off-loop under the async auth lock. At minimum, store the resolved credentials on _api_client and wrap google.auth.default() and creds.refresh() in asyncio.to_thread.

Workaround

We build one genai.Client(credentials=creds) per process, in a thread. We keep creds FRESH by calling creds.refresh() via asyncio.to_thread whenever creds.token_state is not TokenState.FRESH. valid turns False at the same REFRESH_THRESHOLD, so connect() never takes the sync branch. With the same ticker, max stall per connect drops to 9–28 ms.

主要言語
Python
スター
4k
フォーク
1k
平均マージ
1日 17時間
マージ済み PR（30日）
52

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

googleapis/python-genai のほかの issue

googleapis/python-genai の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。