SocketException / UnobservedTaskException

[elajeunesse]

Following an upgrade of FeatBit.ServerSdk from 1.2.0 to 1.2.9 we started seeing System.Net.Sockets.SocketException being observed by the mechanism UnobservedTaskException

I noticed that the client SDK received a potential similar fix that could potentially be applied to the server side SDK. Are there any current plans to apply a similar change on the server side?

[deleteLater]

Thanks for catching this, could you provide the stack trace of the unhandled exception which might help us to identify the issue?

[elajeunesse]

Not much of one, but here's what we have:

System.Net.Sockets.SocketException: Operation canceled
  at void AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)()
  at void ValueTaskSourceAsTask.s_completionAction(object state)()
  at async Task TcpClient.CompleteConnectAsync(Task task)()
System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread.

[deleteLater]

Hi @elajeunesse , sorry for the late update. We’ve released version v1.2.10 and you can give it a try to see if it resolves your issue.

[elajeunesse]

@deleteLater Note this is still happening for us on v1.2.10, I did have Copilot search through the updated codebase and it found these not yet fixed:

_ = ReconnectAsync() | ConnectAsync catch block
_ = ReconnectAsync() | HandleConnectionCloseAsync
_ = OnClosed?.Invoke(...) | CompleteClose
_ = OnKeepAlive?.Invoke() | KeepAliveAsync
_ = OnConnected?.Invoke() | ConnectAsync
_ = OnReconnecting?.Invoke() | ReconnectAsync
_ = OnReconnected?.Invoke() | ReconnectAsync

If you believe these are non-problematic, let us know - thanks!

[deleteLater]

I did notice these fire-and-forget patterns when I working on PR #31 and I reviewed them again

1. ReconnectAsync won't throw because exceptions are handled internally
2. OnClosed and OnReconnecting handlers won't throw
3. OnKeepAlive and OnReconnected currently has no handler, so they won't throw either
4. OnConnected handler is wrapped in a try/catch block, so it never throws

So for current implementation, they won't cause the UnobservedTaskException. Since the stack trace didn't include much information, could you provide more details, such as

1. Does this exception occur frequently?
2. Does it occur randomly, or are there specific conditions that trigger it?
3. Can you reproduce this error on your machine? If so, you can try setting the FeatBit log level to Trace so we can gather more information.
4. What is your project environment (WPF, UWP, etc...)?