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

Track deferred ElevenLabs webhook transcription and conversational voice APIs

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
typescript
领域
observability

调研方向

先阅读 issue #2293 和现有的 request/response tracing 集成,然后检查列出的 ElevenLabs 入口点:webhook transcription、SpeechEngine.Server、SpeechEngine.Session 和 conversational voice APIs。在实现之前,先定义异步作业和入站会话的 tracing 契约,包括关联、span 生命周期、断开连接时的行为以及最终输出。完成标准是:真实的端到端生命周期测试能够保留现有的 request/response trace 契约,同时不会将 acknowledgements 或出站文本视为已完成的生成。

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

描述

never-stale

Sub-issue of #2293 tracking the remaining conversational execution surfaces from that issue, plus asynchronous transcription mode. These APIs are intentionally excluded from the current request/response instrumentation.

Deferred surfaces:

  • client.speechToText.convert({ ..., webhook: true }): the request returns an acknowledgement and the transcription arrives at a separately configured webhook.
  • client.speechEngine.attach(...) and SpeechEngine.Server: inbound WebSocket session handling rather than an application-initiated model request returning its result.
  • SpeechEngine.Session transcript callbacks and session.sendResponse(...): the application receives inbound transcripts and sends response text to ElevenLabs; sending text does not return the synthesized audio to that application process. Session lifecycle/listener methods are also uninstrumented.
  • Conversational voice connection/run APIs mentioned in #2293: verify the exact package and execution entrypoints before implementation. Browser voice connections are provided by the separate @elevenlabs/client SDK; client.conversationalAi REST authentication and management endpoints should not be treated as model-generation calls merely because they relate to agents.

Future work needs an explicit tracing contract for asynchronous jobs or inbound conversational sessions: correlation across requests/processes, span ownership and lifetime, cancellation/disconnect behavior, and how final outputs are captured. Do not represent job acknowledgements or outbound response text as completed model generations.

The current implementation deliberately removes Speech Engine instrumentation from both manual and automatic paths and skips webhook transcription. Any future coverage should include realistic lifecycle e2e tests and preserve the request/response integration's existing trace contract.

主要语言
TypeScript
星标
29
派生
18
平均合并
1 天 15 小时
30 天内合并 PR
69

环境准备

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

从这里开始

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

braintrustdata/braintrust-sdk-javascript 的其他 Issue

查看 braintrustdata/braintrust-sdk-javascript 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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