-
Notifications
You must be signed in to change notification settings - Fork 58
Replace sfu connect exception with sfu connect failure domain model #1745
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
rahul-lohra
wants to merge
3
commits into
fix/sfu-join-self-triggered-reconnect
from
fix/rahullohra/replace-sfu-connect-exception-with-sfu-connect-failure
Closed
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
45 changes: 45 additions & 0 deletions
45
...eo-android-core/src/main/kotlin/io/getstream/video/android/core/call/SfuConnectFailure.kt
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,45 @@ | ||
| /* | ||
| * Copyright (c) 2014-2026 Stream.io Inc. All rights reserved. | ||
| * | ||
| * Licensed under the Stream License; | ||
| * you may not use this file except in compliance with the License. | ||
| * You may obtain a copy of the License at | ||
| * | ||
| * https://github.com/GetStream/stream-video-android/blob/main/LICENSE | ||
| * | ||
| * Unless required by applicable law or agreed to in writing, software | ||
| * distributed under the License is distributed on an "AS IS" BASIS, | ||
| * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
| * See the License for the specific language governing permissions and | ||
| * limitations under the License. | ||
| */ | ||
|
|
||
| package io.getstream.video.android.core.call | ||
|
|
||
| /** | ||
| * Typed SFU connect failure produced by [RtcSession.connectInternal]. | ||
| */ | ||
| internal sealed interface SfuConnectFailure { | ||
| val error: Exception | ||
|
|
||
| /** | ||
| * [RtcSession.connectInternal] stopped waiting for the socket to reach a terminal state. | ||
| */ | ||
| data class SocketStateObservationTimeout( | ||
| override val error: Exception, | ||
| ) : SfuConnectFailure | ||
|
|
||
| /** | ||
| * The socket failure is already being recovered by [RtcSession.stateJob]. | ||
| */ | ||
| data class RecoverableSocketFailure( | ||
| override val error: Exception, | ||
| ) : SfuConnectFailure | ||
|
|
||
| /** | ||
| * The socket failure should fail immediately without recovery. | ||
| */ | ||
| data class TerminalSocketFailure( | ||
| override val error: Exception, | ||
| ) : SfuConnectFailure | ||
| } |
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🔴 Critical | ⚡ Quick win
SocketStateObservationTimeoutbranch never awaits the REJOIN it triggers —_join()falls through toSuccess.Unlike the
RecoverableSocketFailurebranch, this branch firesscope.launch { reconnect(REJOIN, ...) }and then falls out of thewhenwith noreturn, straight intoval connectedSession = session.value ?: return Failure(...)(Line 829). Sincesession.valueis already non-null (set at Line 773 beforeconnectInternal()ran), execution proceeds tomonitorSession(...)andreturn Success(...)immediately — without ever observing whether the REJOIN succeeded.This contradicts
JoinRecoverableFailureTest.socket state observation timeout starts a REJOIN itself, which expects_join()to stay suspended after triggering REJOIN and resolve toFailureonly once the connection settles asReconnectingFailed. As written,_join()returnsSuccesssynchronously, so that test would fail, and in production the join flow would falsely report success while the SFU connection actually timed out.🐛 Proposed fix to await the triggered REJOIN, mirroring the RecoverableSocketFailure branch
is SfuConnectFailure.SocketStateObservationTimeout -> { logger.w { "[_join] SFU socket state observation timed out with no recovery started — triggering REJOIN" } scope.launch { reconnect( WebsocketReconnectStrategy.WEBSOCKET_RECONNECT_STRATEGY_REJOIN, "join-recoverable-connect-failure", ) } + if (!didReconnectSucceed()) { + logger.e { "[_join] Could not recover from socket state observation timeout. Error : $sfuConnectionResult" } + sendJoinErrorAnalytics(sfuConnectionResult) + return Failure( + Error.GenericError( + sfuConnectionResult.cause.error.message ?: "SFU connection timed out", + ), + ) + } }📝 Committable suggestion
🤖 Prompt for AI Agents