Skip to content

Conversation

@PVince81
Copy link
Member

In some concurrent request scenarios, the session of a participant might
expire just after its id got retrieved. To avoid unexpected behavior, if
the participant could not be found by session id, fall back to getting
it by user id.

Fixes issue where a room can sometimes not be deleted from the UI due to
a concurrent request that removes the session id.

Fixes #5733

In some concurrent request scenarios, the session of a participant might
expire just after its id got retrieved. To avoid unexpected behavior, if
the participant could not be found by session id, fall back to getting
it by user id.

Fixes issue where a room can sometimes not be deleted from the UI due to
a concurrent request that removes the session id.

Signed-off-by: Vincent Petry <[email protected]>
@PVince81
Copy link
Member Author

/backport to stable21.1

@PVince81 PVince81 merged commit 1e8f03a into master Jun 10, 2021
@PVince81 PVince81 deleted the bugfix/5733/fallback-getparticipant branch June 10, 2021 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Random 404 when deleting room with session

3 participants