wx44wx/pipecat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Revert "fix context order when using interruption strategies"

Browse Source 
This reverts commit de8ee96927.
This commit is contained in:
Aleix Conchillo Flaqué
2025-10-07 17:42:35 -07:00
parent d9aef5f916
commit 7c15a8c800
6 changed files with 15 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
src/pipecat/frames/frames.py
View File

@@ -849,15 +849,13 @@ class FrameProcessorResumeUrgentFrame(SystemFrame):
class InterruptionFrame(SystemFrame):
"""Frame indicating user started speaking (interruption detected).
Usually emitted by the pipeline task to indicate that all frame processors
should be interrrupted.
Parameters:
pushed_by_task: Whether this interruption was pushed from the pipeline
task.
Emitted by the BaseInputTransport to indicate that a user has started
speaking (i.e. is interrupting). This is similar to
UserStartedSpeakingFrame except that it should be pushed concurrently
with other frames (so the order is not guaranteed).
"""
pushed_by_task: bool = False
pass
@dataclass
@@ -888,17 +886,6 @@ class StartInterruptionFrame(InterruptionFrame):
)
@dataclass
class InterruptionCompletedFrame(SystemFrame):
"""Frame indicating that the whole pipeline has been interrupted.
This is emitted by the pipeline task when an InterruptionFrame has made it
all the way to the end of pipeline, interrupting all the frame processors.
"""
pass
@dataclass
class UserStartedSpeakingFrame(SystemFrame):
"""Frame indicating user has started speaking.