fix(console): set mock participant state to active#5645
Merged
Conversation
The mock room's remote participant didn't have a state set, so wait_for_participant (which now requires PARTICIPANT_STATE_ACTIVE since #5271) hangs in console mode.
chenghao-mou
approved these changes
May 6, 2026
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
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.
Summary
wait_for_participantwas changed in fix: wait_for_participant waits until participant is fully active #5271 to requirePARTICIPANT_STATE_ACTIVE, but the mock participant increate_mock_roomhad nostateset, so the call hangs in console mode.state = PARTICIPANT_STATE_ACTIVEon the mock remote participant.Fixes the issue raised in #5271 (comment).