Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
  • 哪里不对？
#3,056 2 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@Venkaiahbabuneelam 已经在做这个了。

开始于 2026年10月6日。

评估

难度
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 内容生成。

描述

priority: p2 type: bug
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 小时
30 天内合并 PR
54

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

googleapis/python-genai 的其他 Issue

查看 googleapis/python-genai 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。