Cairn

TTS sync pipeline plays wrong audio path bug

NousResearch/hermes-agent · cluster 115029

Data as of

Nothing open on GitHub. Fix merged in #116792. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #116792. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #116792. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where the sync speaker pipeline plays the wrong audio artifact when the TTS provider writes to a different path than requested, causing sentences to be silently dropped or skipped. Multiple fix attempts and related issues address this same path mismatch problem.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #116792 fix(tts): voice mode plays sentences whose audio the provider wrote at a different path (#115029, salvage #115046)

    merged to main

    files: tests/tools/test_tts_streaming.py, tools/tts_tool_speaker.py

3 PRs closed without merging

From the close comments: done elsewhere 2 · merged via another change 1

  • #115046 fix(tts): play the artifact the tool reported in the sync speaker pipeline · merged via another change → 77fd944, #116792, #115029, #115046
  • #115078 fix(tts): the sync speaker pipeline plays the artifact the provider reports (#115029) · done elsewhere → 77fd944, #116792, #115029, #115046
  • #115314 fix(tts): play the artifact text_to_speech_tool reports, not the requested stub · done elsewhere → 77fd944, #116792, #115029, #115046
Closed issues · 1
  • Closed#115029[Bug]: sync speaker pipeline silently drops every sentence when the TTS provider writes a different path than requested
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs
#116792
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
20 Sep 2026

For your agent

The same facts, typed.

cluster/115029.json
cluster/115029.md