-
Notifications
You must be signed in to change notification settings - Fork 309
fix(voice/room_io): non-delta transcription final-stream races #1765
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
tsushanth
wants to merge
1
commit into
livekit:main
Choose a base branch
from
tsushanth:fix/non-delta-transcription-final-text
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+104
−5
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| --- | ||
| '@livekit/agents': patch | ||
| --- | ||
|
|
||
| Fix `ParticipantTranscriptionOutput` non-delta final-stream publishing two | ||
| races that surfaced with Deepgram-style mid-utterance final bursts. | ||
|
|
||
| 1. `handleFlush()` previously read `this.latestText` from inside | ||
| `flushTaskImpl`, so a `captureText()` for the next segment landing | ||
| before the flush task ran would overwrite the field and cause segment | ||
| A's `lk.transcription_final: "true"` stream to publish segment B's | ||
| text. The text to flush is now snapshotted when the task is scheduled | ||
| and passed in as a parameter. | ||
|
|
||
| 2. When the first event for a fresh segment was already `is_final`, | ||
| `handleCaptureText` called `resetState()` after `captureText` had set | ||
| `latestText`, clearing it back to `""`. The subsequent final stream | ||
| then published an empty string. `latestText` is now restored from the | ||
| captured payload immediately after `resetState()` so the same-tick | ||
| final preserves the captured text. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚩 currentId is not snapshotted in handleFlush, relying on await ordering for correctness
The PR correctly snapshots
latestTextinhandleFlush()at_output.ts:224, butcurrentIdis still read fromthis.currentIdlazily insideflushTaskImpl→createTextWriterat_output.ts:247. This is safe in the normal capture→flush flow becausehandleCaptureTextat_output.ts:186-188awaits the pending flush task before callingresetState()(which generates a newcurrentId). However,setParticipant()at_output.ts:68-69callsflush()thenresetState()synchronously without awaiting the flush task. IfsetParticipantis called while a flush task is in-flight, the flush could pick up the new segment ID. This is a pre-existing issue not introduced by this PR, but it's worth noting the asymmetry:latestTextis now robustly snapshotted whilecurrentIdrelies on caller ordering.Was this helpful? React with 👍 or 👎 to provide feedback.