Handle failures during socket connection

[gpunto]

Goal

We were missing onFailure handling during socket connection so, in case of errors there, we were never completing the coroutine

Implementation

Override onFailure for the StreamWebSocketListener used during connection.

Testing

Try launching the sample without network connection and verify that the suspend function throws instead of never completing.

Checklist

• Issue linked (if any)
• Tests/docs updated
• I have signed the Stream CLA (required for external contributors)

[github-actions]

PR checklist ✅

All required conditions are satisfied:

• Title length is OK (or ignored by label).
• At least one pr: label exists.
• Sections ### Goal, ### Implementation, and ### Testing are filled.

🎉 Great job! This PR is ready for review.

[Copilot]

Pull Request Overview

This PR fixes a bug where socket connection failures during handshake were not properly handled, causing coroutines to never complete. The fix overrides the onFailure method in the StreamWebSocketListener to properly propagate connection failures.

• Added onFailure handling in the handshake WebSocket listener to complete coroutines on connection errors
• Added comprehensive test coverage for the socket connection failure scenario

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
StreamSocketSession.kt	Added onFailure override to handle socket connection failures during handshake
StreamSocketSessionTest.kt	Added test case and updated imports to verify proper failure handling behavior

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[VelikovPetar]

Looks good to me!
This reminded me, is closing the socket in this scenario a possible occurrence? I cannot think of a case where onClosed would be called here, but perhaps we should handle it as well - WDYT?

[gpunto]

Looks good to me! This reminded me, is closing the socket in this scenario a possible occurrence? I cannot think of a case where onClosed would be called here, but perhaps we should handle it as well - WDYT?

Good point! What do you think we should do in that case? Resume with a custom exception?

Edit: done, let me know if it makes sense!