Post History

The source code for the Socket.AcceptAsync class seems to be [this one](https://github.com/dotnet/runtime/blob/adfae48391d47338d620c970d64a4bdec64fa7f8/src/libraries/System.Net.Sockets/src/System/Net/Sockets/Socket.cs#L2677).

The relevant code (the one related to exceptions being raised) is the following:

```c#
private bool AcceptAsync(SocketAsyncEventArgs e, CancellationToken cancellationToken)
{
	ThrowIfDisposed();

	ArgumentNullException.ThrowIfNull(e);
	if (e.HasMultipleBuffers)
	{
		throw new ArgumentException(SR.net_multibuffernotsupported, nameof(e));
	}
	if (_rightEndPoint == null)
	{
		throw new InvalidOperationException(SR.net_sockets_mustbind);
	}
	if (!_isListening)
	{
		throw new InvalidOperationException(SR.net_sockets_mustlisten);
	}

	SocketError socketError;
	try
	{
		socketError = e.DoOperationAccept(this, _handle, acceptHandle, cancellationToken);
	}
	catch (Exception ex)
	{
		SocketsTelemetry.Log.AfterAccept(SocketError.Interrupted, ex.Message);

		// Clear in-use flag on event args object.
		e.Complete();
		throw;
	}

	return socketError == SocketError.IOPending;
}
```

Based on this, I would consider handling the following exception types:

- ObjectDisposedException 
- ArgumentNullException
- InvalidOperationException
- Exception (that is, even the library creators expect "other" exception types)