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

CHANGELOG.md: task.cancel() and EndFrame clarification

Browse Source
This commit is contained in:
Aleix Conchillo Flaqué
2025-01-31 18:30:48 -08:00
parent 11aeb68ddb
commit 95f0dbf3f3
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
CHANGELOG.md
View File

@@ -73,11 +73,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
### Other ### Other
- Updated all examples to use `task.cancel()` instead of pushing an `EndFrame` - Updated examples to use `task.cancel()` to immediately exit the example when a
when a participant leaves/disconnects. If you push an `EndFrame` this will participant leaves or disconnects, instead of pushing an `EndFrame`. Pushing
cause the bot to run through everything that is internally queued (which could an `EndFrame` causes the bot to run through everything that is internally
take seconds). Instead, if a participant disconnects there is nothing else to queued (which could take some seconds). Note that using `task.cancel()` might
be sent and therefore we should stop immediately. not always be the best option and pushing an `EndFrame` could still be
desirable to make sure all the pipeline is flushed.
## [0.0.54] - 2025-01-27 ## [0.0.54] - 2025-01-27