Realtime: complete port of fixes and tests for sendinputaudio behavior #333
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The changes in #303 were incompletely migrated into #301. This PR completes the functional migration and remedies the remaining bug with
SendInputAudioAsync(BinaryData).Most importantly: the boolean sentinel for audio sending is only set and reset when sending a stream, while single-payload sends are fully locked.
This is more efficiently and elegantly accomplished via a
SemaphoreSlim(with a wrapping pair of extension methods to simplify the try/finally patterns).Test coverage that validates intended behavior was also ported.