Decide how DefaultAbly methods should respond to cancellation

[lawrence-forooghian]

The methods in DefaultAbly do not all cooperate with cancellation. For example, due to its use of suspendCoroutine (as opposed to suspendCancellableCoroutine), the suspending version of connect is not cancellable.

The implication of this is that if, for example, connect is called from within a withTimeout block, the withTimeout call will not return even if the timeout elapses before connect returns.

This has implications on our unit tests, which need to work around this lack of cancellability. I do not know if it has any implications for the public API of the library – for example, whether it impacts users’ ability to wrap Publisher methods in a withTimeout block.

We should understand the implications and decide if/how to address them.

[sync-by-unito]

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3246