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

Agent stays "speaking" forever when the avatar participant leaves mid-reply

未关闭
#8,027 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@regalmoix 已经在做这个了。

开始于 2026年10月21日。

  • #8028 来自 @regalmoix —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
54/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
python

调研方向

Start by locating DataStreamAudioOutput and its playout wait and clear-buffer timeout handling, then compare the Synthesia plugin's participant-disconnect teardown. Trace how participant_disconnected should release a pending segment, including after the avatar rejoins; done means pending playout completes as interrupted and the agent no longer stays in speaking.

由索引模型根据 Issue 内容生成。

描述

Title: Agent stays "speaking" forever when the avatar participant leaves mid-reply

With any avatar built on DataStreamAudioOutput, if the avatar participant disconnects while a reply is pending, lk.playback_finished never arrives. wait_for_playout() has no timeout, so the agent stays speaking until the user interrupts. With allow_interruptions=False, or a user waiting in silence, it never recovers.

It also stays stuck after the avatar rejoins with the same identity: the old segment is never finished, so every later playout wait is behind it.

Repro

  1. Start an AgentSession with an avatar plugin (e.g. Anam).
  2. session.say("<long text>", allow_interruptions=False)
  3. Mid-reply, remove the avatar participant. Killing the avatar worker also works once the server's departure timeout fires.
  4. The speech never completes; agent_state stays speaking.

DataStreamAudioOutput doesn't listen for participant_disconnected at all. Only the Synthesia plugin handles avatar loss, and its teardown doesn't release pending playout either.

Expected: pending playout completes as interrupted, the same as the existing clear-buffer timeout fallback.

主要语言
Python
星标
14.6k
派生
3.9k
平均合并
3 天 11 小时
30 天内合并 PR
196

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

livekit/agents 的其他 Issue

查看 livekit/agents 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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